Web server controls for web enabled recognition and/or audible prompting

ABSTRACT

Web server controls are provided for generating client side markups with recognition and/or audible prompting. Three approaches are disclosed for implementation of the controls.

CROSS-REFERENCE TO RELATED APPLICATON

[0001] The present application is a continuation-in-part and claimspriority of U.S. patent application entitled WEB SERVE CONTROLS FOR WEBENABLED RECOGNITION AND/OR AUDIBLE PROMPTING having Ser. No. 10/046,131,filed Oct. 21, 2001.

BACKGROUND OF THE INVENTION

[0002] The present invention relates to access of information over anetwork such as the Internet. More particularly, the present inventionrelates to controls for a server that generates client side markupenabled with recognition and/or audible prompting.

[0003] Small computing devices such as personal digital assistants(PDA), devices and portable phones are used with ever increasingfrequency by people in their day-to-day activities. With the increase inprocessing power now available for microprocessors used to run thesedevices, the functionality of these devices is increasing, and in somecases, merging. For instance, many portable phones now can be used toaccess and browse the Internet as well as can be used to store personalinformation such as addresses, phone numbers and the like.

[0004] In view that these computing devices are being used for browsingthe Internet, or are used in other server/client architectures, it istherefore necessary to enter information into the computing device.Unfortunately, due to the desire to keep these devices as small aspossible in order that they are easily carried, conventional keyboardshaving all the letters of the alphabet as isolated buttons are usuallynot possible due to the limited surface area available on the housingsof the computing devices.

[0005] To address this problem, there has been increased interest andadoption of using voice or speech to access information over a wide areanetwork such as the Internet. For example, voice portals such as throughthe use of VoiceXML (voice extensible markup language) have beenadvanced to allow Internet content to be accessed using only atelephone. In this architecture, a document server (for example, a webserver) processes requests from a client through a VoiceXML interpreter.The web server can produce VoiceXML documents in reply, which areprocessed by the VoiceXML interpreter and rendered audibly to the user.Using voice commands through voice recognition, the user can navigatethe web.

[0006] Generally, there are two techniques of “speech enabling”information or web content. In the first technique, existing visualmarkup language pages typically visually rendered by a device having adisplay are interpreted and rendered aurally. However, this approachoften yields poor results because markup meant for visual interactionusually do not have enough information to create a sensible aural dialogautomatically. In addition, voice interaction is prone to error,especially over noisy channels such as a telephone. Without visual orother forms of persistent feedback, navigation through the web serverapplication can be extremely difficult for the user. This approach thusrequires mechanisms such as help messages, which are also renderedaudibly to the user in order to help them navigate through the website.The mechanisms are commonly referred to as “voice dialogs”, which alsomust address errors when incorrect information or no information isprovided by the user, for example, in response to an audible question.Since the mechanisms are not commonly based on the visual content of theweb page, they cannot be generated automatically, and thereforetypically require extensive development time by the applicationdeveloper.

[0007] A second approach to speech enabling web content includes writingspecific voice pages in a new language. An advantage of this approach isthat the speech-enabled page contains all the mechanisms needed foraural dialog such as repairs and navigational help. However, asignificant disadvantage is that the application pages must then beadapted to include the application logic as found in the visual contentpages. In other words, the application logic of the visual content pagesmust be rewritten in the form of the speech-enabling language. Even whenthis process can be automated by the use of tools creating visual andaural pages from the same specification, maintenance of the visual andspeech enabled pages is usually difficult to synchronize. In addition,this approach does not easily allow multimodal applications, for examplewhere both visual and speech interaction is provided on the web page.Since the visual and speech-enabled pages are unrelated, the input andoutput logic is not easily coordinated to work with each other.

[0008] To date, speech interaction authoring is also cumbersome due tothe organization or format currently used as the interface. Generally,the speech interface either tends to be tied too closely to the businesslogic of the application, which inhibits re-use of the elements of thespeech interface in other applications, or the speech interface is toorestricted by a simplistic dialog model (e.g. forms and fields).

[0009] There is thus an ongoing need to improve upon the architectureand methods used to provide speech recognition in a server/clientarchitecture such as the Internet. In particular, a method, system orauthoring tool that addresses one, several or all of the foregoingdisadvantages and thus provides generation of speech-enabled recognitionand/or speech-enabled prompting of client markup from a web server isneeded.

SUMMARY OF THE INVENTION

[0010] Web server controls are provided for generating client sidemarkups with recognition and/or audible prompting. Three approaches aredisclosed for implementation of the controls.

[0011] In a first approach, controls commonly related to visualrendering are extended to include an attributes related to recognitionand/or audible prompting. Typically, controls such as “label” use alibrary having markup information, which provides a visual prompt on adisplay. Similarly, “textbox” provides an input field on a visualdisplay. In the first approach, an additional library is provided forrecognition and/or audibly prompting, wherein the controls includeattributes or parameters to use both libraries.

[0012] In a second approach, the controls access the current, existinglibrary for visual markup information, but include attributes andmechanisms to perform recognition and/or audible prompting. In otherwords, the controls use the library, but only when visual rendering isdesired.

[0013] In a third approach, a set of companion controls havingattributes related to recognition and/or audible prompting are formed.The companion controls use a library having recognition and audiblyprompting markup information. The companion controls are selectivelyassociated with visual controls. In this manner, application logicremains with the visual controls, wherein the companion controls providerecognized results to the visual controls. The companion controls followa dialog in that controls are provided for prompting a question,obtaining an answer, confirming a result, providing a command, or makinga statement. A question/answer control can also be formed from one ormore of these controls in order to form a dialog or sub-dialogpertaining to a specific topic.

BRIEF DESCRIPTION OF THE DRAWINGS

[0014]FIG. 1 is a plan view of a first embodiment of a computing deviceoperating environment.

[0015]FIG. 2 is a block diagram of the computing device of FIG. 1.

[0016]FIG. 3 is a block diagram of a general purpose computer.

[0017]FIG. 4 is a block diagram of an architecture for a client/serversystem.

[0018]FIG. 5 is a display for obtaining credit card information.

[0019]FIG. 6 is an exemplary page of mark-up language executable on aclient having a display and voice recognition capabilities.

[0020]FIG. 7 is a block diagram illustrating a first approach forproviding recognition and audible prompting in client side markups.

[0021]FIG. 8 is a block diagram illustrating a second approach forproviding recognition and audible prompting in client side markups.

[0022]FIG. 9 is a block diagram illustrating a third approach forproviding recognition and audible prompting in client side markups.

[0023]FIG. 10 is a block diagram illustrating companion controls.

[0024]FIG. 11 is a detailed block diagram illustrating companioncontrols of a first embodiment.

[0025]FIG. 12 is a block diagram illustrating companion controls of asecond embodiment.

[0026]FIG. 13 is a block diagram illustrating speech controlsinheritance for the second embodiment.

DETAILED DESCRIPTION OF THE ILLUSTRATIVE EMBODIMENTS

[0027] Before describing architecture of web based recognition andmethods for implementing the same, it may be useful to describegenerally computing devices that can function in the architecture.Referring now to FIG. 1, an exemplary form of a data management device(PIM, PDA or the like) is illustrated at 30. However, it is contemplatedthat the present invention can also be practiced using other computingdevices discussed below, and in particular, those computing deviceshaving limited surface areas for input buttons or the like. For example,phones and/or data management devices will also benefit from the presentinvention. Such devices will have an enhanced utility compared toexisting portable personal information management devices and otherportable electronic devices, and the functions and compact size of suchdevices will more likely encourage the user to carry the device at alltimes. Accordingly, it is not intended that the scope of thearchitecture herein described be limited by the disclosure of anexemplary data management or PIM device, phone or computer hereinillustrated.

[0028] An exemplary form of a data management mobile device 30 isillustrated in FIG. 1. The mobile device 30 includes a housing 32 andhas an user interface including a display 34, which uses a contactsensitive display screen in conjunction with a stylus 33. The stylus 33is used to press or contact the display 34 at designated coordinates toselect a field, to selectively move a starting position of a cursor, orto otherwise provide command information such as through gestures orhandwriting. Alternatively, or in addition, one or more buttons 35 canbe included on the device 30 for navigation. In addition, other inputmechanisms such as rotatable wheels, rollers or the like can also beprovided. However, it should be noted that the invention is not intendedto be limited by these forms of input mechanisms. For instance, anotherform of input can include a visual input such as through computervision.

[0029] Referring now to FIG. 2, a block diagram illustrates thefunctional components comprising the mobile device 30. A centralprocessing unit (CPU) 50 implements the software control functions. CPU50 is coupled to display 34 so that text and graphic icons generated inaccordance with the controlling software appear on the display 34. Aspeaker 43 can be coupled to CPU 50 typically with a digital-to-analogconverter 59 to provide an audible output. Data that is downloaded orentered by the user into the mobile device 30 is stored in anon-volatile read/write random access memory store 54 bi-directionallycoupled to the CPU 50. Random access memory (RAM) 54 provides volatilestorage for instructions that are executed by CPU 50, and storage fortemporary data, such as register values. Default values forconfiguration options and other variables are stored in a read onlymemory (ROM) 58. ROM 58 can also be used to store the operating systemsoftware for the device that controls the basic functionality of themobile 30 and other operating system kernel functions (e.g., the loadingof software components into RAM 54).

[0030] RAM 54 also serves as a storage for the code in the manneranalogous to the function of a hard drive on a PC that is used to storeapplication programs. It should be noted that although non-volatilememory is used for storing the code, it alternatively can be stored involatile memory that is not used for execution of the code.

[0031] Wireless signals can be transmitted/received by the mobile devicethrough a wireless transceiver 52, which is coupled to CPU 50. Anoptional communication interface 60 can also be provided for downloadingdata directly from a computer (e.g., desktop computer), or from a wirednetwork, if desired. Accordingly, interface 60 can comprise variousforms of communication devices, for example, an infrared link, modem, anetwork card, or the like.

[0032] Mobile device 30 includes a microphone 29, and analog-to-digital(A/D) converter 37, and an optional recognition program (speech, DTMF,handwriting, gesture or computer vision) stored in store 54. By way ofexample, in response to audible information, instructions or commandsfrom a user of device 30, microphone 29 provides speech signals, whichare digitized by A/D converter 37. The speech recognition program canperform normalization and/or feature extraction functions on thedigitized speech signals to obtain intermediate speech recognitionresults. Using wireless transceiver 52 or communication interface 60,speech data is transmitted to a remote recognition server 204 discussedbelow and illustrated in the architecture of FIG. 5. Recognition resultsare then returned to mobile device 30 for rendering (e.g. visual and/oraudible) thereon, and eventual transmission to a web server 202 (FIG.5), wherein the web server 202 and mobile device 30 operate in aclient/server relationship. Similar processing can be used for otherforms of input. For example, handwriting input can be digitized with orwithout pre-processing on device 30. Like the speech data, this form ofinput can be transmitted to the recognition server 204 for recognitionwherein the recognition results are returned to at least one of thedevice 30 and/or web server 202. Likewise, DTMF data, gesture data andvisual data can be processed similarly. Depending on the form of input,device 30 (and the other forms of clients discussed below) would includenecessary hardware such as a camera for visual input.

[0033] In addition to the portable or mobile computing devices describedabove, it should also be understood that the present invention can beused with numerous other computing devices such as a general desktopcomputer. For instance, the present invention will allow a user withlimited physical abilities to input or enter text into a computer orother computing device when other conventional input devices, such as afull alpha-numeric keyboard, are too difficult to operate.

[0034] The invention is also operational with numerous other generalpurpose or special purpose computing systems, environments orconfigurations. Examples of well known computing systems, environments,and/or configurations that may be suitable for use with the inventioninclude, but are not limited to, wireless or cellular telephones,regular telephones (without any screen), personal computers, servercomputers, hand-held or laptop devices, multiprocessor systems,microprocessor-based systems, set top boxes, programmable consumerelectronics, network PCs, minicomputers, mainframe computers,distributed computing environments that include any of the above systemsor devices, and the like.

[0035] The following is a brief description of a general purposecomputer 120 illustrated in FIG. 3. However, the computer 120 is againonly one example of a suitable computing environment and is not intendedto suggest any limitation as to the scope of use or functionality of theinvention. Neither should the computer 120 be interpreted as having anydependency or requirement relating to any one or combination ofcomponents illustrated therein.

[0036] The invention may be described in the general context ofcomputer-executable instructions, such as program modules, beingexecuted by a computer. Generally, program modules include routines,programs, objects, components, data structures, etc. that performparticular tasks or implement particular abstract data types. Theinvention may also be practiced in distributed computing environmentswhere tasks are performed by remote processing devices that are linkedthrough a communications network. In a distributed computingenvironment, program modules may be located in both local and remotecomputer storage media including memory storage devices. Tasks performedby the programs and modules are described below and with the aid offigures. Those skilled in the art can implement the description andfigures as processor executable instructions, which can be written onany form of a computer readable medium.

[0037] With reference to FIG. 3, components of computer 120 may include,but are not limited to, a processing unit 140, a system memory 150, anda system bus 141 that couples various system components including thesystem memory to the processing unit 140. The system bus 141 may be anyof several types of bus structures including a memory bus or memorycontroller, a peripheral bus, and a local bus using any of a variety ofbus architectures. By way of example, and not limitation, sucharchitectures include Industry Standard Architecture (ISA) bus,Universal Serial Bus (USB), Micro Channel Architecture (MCA) bus,Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA)local bus, and Peripheral Component Interconnect (PCI) bus also known asMezzanine bus. Computer 120 typically includes a variety of computerreadable mediums. Computer readable mediums can be any available mediathat can be accessed by computer 120 and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer readable mediums may comprise computerstorage media and communication media. Computer storage media includesboth volatile and nonvolatile, removable and non-removable mediaimplemented in any method or technology for storage of information suchas computer readable instructions, data structures, program modules orother data. Computer storage media includes, but is not limited to, RAM,ROM, EEPROM, flash memory or other memory technology, CD-ROM, digitalversatile disks (DVD) or other optical disk storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or any other medium which can be used to store the desired informationand which can be accessed by computer 120.

[0038] Communication media typically embodies computer readableinstructions, data structures, program modules or other data in amodulated data signal such as a carrier wave or other transportmechanism and includes any information delivery media. The term“modulated data signal” means a signal that has one or more of itscharacteristics set or changed in such a manner as to encode informationin the signal. By way of example, and not limitation, communicationmedia includes wired media such as a wired network or direct-wiredconnection, and wireless media such as acoustic, FR, infrared and otherwireless media. Combinations of any of the above should also be includedwithin the scope of computer readable media.

[0039] The system memory 150 includes computer storage media in the formof volatile and/or nonvolatile memory such as read only memory (ROM) 151and random access memory (RAM) 152. A basic input/output system 153(BIOS), containing the basic routines that help to transfer informationbetween elements within computer 120, such as during start-up, istypically stored in ROM 151. RAM 152 typically contains data and/orprogram modules that are immediately accessible to and/or presentlybeing operated on by processing unit 140. By way of example, and notlimitation, FIG. 3 illustrates operating system 54, application programs155, other program modules 156, and program data 157.

[0040] The computer 120 may also include other removable/non-removablevolatile/nonvolatile computer storage media. By way of example only,FIG. 3 illustrates a hard disk drive 161 that reads from or writes tonon-removable, nonvolatile magnetic media, a magnetic disk drive 171that reads from or writes to a removable, nonvolatile magnetic disk 172,and an optical disk drive 175 that reads from or writes to a removable,nonvolatile optical disk 176 such as a CD ROM or other optical media.Other removable/non-removable, volatile/nonvolatile computer storagemedia that can be used in the exemplary operating environment include,but are not limited to, magnetic tape cassettes, flash memory cards,digital versatile disks, digital video tape, solid state RAM, solidstate ROM, and the like. The hard disk drive 161 is typically connectedto the system bus 141 through a non-removable memory interface such asinterface 160, and magnetic disk drive 171 and optical disk drive 175are typically connected to the system bus 141 by a removable memoryinterface, such as interface 170.

[0041] The drives and their associated computer storage media discussedabove and illustrated in FIG. 3, provide storage of computer readableinstructions, data structures, program modules and other data for thecomputer 120. In FIG. 3, for example, hard disk drive 161 is illustratedas storing operating system 164, application programs 165, other programmodules 166, and program data 167. Note that these components can eitherbe the same as or different from operating system 154, applicationprograms 155, other program modules 156, and program data 157. Operatingsystem 164, application programs 165, other program modules 166, andprogram data 167 are given different numbers here to illustrate that, ata minimum, they are different copies.

[0042] A user may enter commands and information into the computer 120through input devices such as a keyboard 182, a microphone 183, and apointing device 181, such as a mouse, trackball or touch pad. Otherinput devices (not shown) may include a joystick, game pad, satellitedish, scanner, or the like. These and other input devices are oftenconnected to the processing unit 140 through a user input interface 180that is coupled to the system bus, but may be connected by otherinterface and bus structures, such as a parallel port, game port or auniversal serial bus (USB). A monitor 184 or other type of displaydevice is also connected to the system bus 141 via an interface, such asa video interface 185. In addition to the monitor, computers may alsoinclude other peripheral output devices such as speakers 187 and printer186, which may be connected through an output peripheral interface 188.

[0043] The computer 120 may operate in a networked environment usinglogical connections to one or more remote computers, such as a remotecomputer 194. The remote computer 194 may be a personal computer, ahand-held device, a server, a router, a network PC, a peer device orother common network node, and typically includes many or all of theelements described above relative to the computer 120. The logicalconnections depicted in FIG. 3 include a local area network (LAN) 191and a wide area network (WAN) 193, but may also include other networks.Such networking environments are commonplace in offices, enterprise-widecomputer networks, intranets and the Internet.

[0044] When used in a LAN networking environment, the computer 120 isconnected to the LAN 191 through a network interface or adapter 190.When used in a WAN networking environment, the computer 120 typicallyincludes a modem 192 or other means for establishing communications overthe WAN 193, such as the Internet. The modem 192, which may be internalor external, may be connected to the system bus 141 via the user inputinterface 180, or other appropriate mechanism. In a networkedenvironment, program modules depicted relative to the computer 120, orportions thereof, may be stored in the remote memory storage device. Byway of example, and not limitation, FIG. 3 illustrates remoteapplication programs 195 as residing on remote computer 194. It will beappreciated that the network connections shown are exemplary and othermeans of establishing a communications link between the computers may beused.

Exemplary Architecture

[0045]FIG. 4 illustrates architecture 200 for web based recognition ascan be used with the present invention. Generally, information stored ina web server 202 can be accessed through mobile device 30 (which hereinalso represents other forms of computing devices having a displayscreen, a microphone, a camera, a touch sensitive panel, etc., asrequired based on the form of input), or through phone 80 whereininformation is requested audibly or through tones generated by phone 80in response to keys depressed and wherein information from web server202 is provided only audibly back to the user.

[0046] In this exemplary embodiment, Architecture 200 is unified in thatwhether information is obtained through device 30 or phone 80 usingspeech recognition, a single recognition server 204 can support eithermode of operation. In addition, architecture 200 operates using anextension of well-known markup languages (e.g. HTML, XHTML, cHTML, XML,WML, and the like). Thus, information stored on web server 202 can alsobe accessed using well-known GUI methods found in these markuplanguages. By using an extension of well-known markup languages,authoring on the web server 202 is easier, and legacy applicationscurrently existing can be also easily modified to include voice or otherforms of recognition.

[0047] Generally, device 30 executes HTML+ scripts, or the like,provided by web server 202. When voice recognition is required, by wayof example, speech data, which can be digitized audio signals or speechfeatures wherein the audio signals have been preprocessed by device 30as discussed above, are provided to recognition server 204 with anindication of a grammar or language model to use during speechrecognition. The implementation of the recognition server 204 can takemany forms, one of which is illustrated, but generally includes arecognizer 211. The results of recognition are provided back to device30 for local rendering if desired or appropriate. Upon compilation ofinformation through recognition and any graphical user interface ifused, device 30 sends the information to web server 202 for furtherprocessing and receipt of further HTML scripts, if necessary.

[0048] As illustrated in FIG. 4, device 30, web server 202 andrecognition server 204 are commonly connected, and separatelyaddressable, through a network 205, herein a wide area network such asthe Internet. It therefore is not necessary that any of these devices bephysically located adjacent to each other. In particular, it is notnecessary that web server 202 includes recognition server 204. In thismanner, authoring at web server 202 can be focused on the application towhich it is intended without the authors needing to know the intricaciesof recognition server 204. Rather, recognition server 204 can beindependently designed and connected to the network 205, and thereby, beupdated and improved without further changes required at web server 202.As discussed below, web server 202 can also include an authoringmechanism that can dynamically generate client-side markups and scripts.In a further embodiment, the web server 202, recognition server 204 andclient 30 may be combined depending on the capabilities of theimplementing machines. For instance, if the client comprises a generalpurpose computer, e.g. a personal computer, the client may include therecognition server 204. Likewise, if desired, the web server 202 andrecognition server 204 can be incorporated into a single machine.

[0049] Access to web server 202 through phone 80 includes connection ofphone 80 to a wired or wireless telephone network 208, that in turn,connects phone 80 to a third party gateway 210. Gateway 210 connectsphone 80 to a telephony voice browser 212. Telephone voice browser 212includes a media server 214 that provides a telephony interface and avoice browser 216. Like device 30, telephony voice browser 212 receivesHTML scripts or the like from web server 202. In one embodiment, theHTML scripts are of the form similar to HTML scripts provided to device30. In this manner, web server 202 need not support device 30 and phone80 separately, or even support standard GUI clients separately. Rather,a common markup language can be used. In addition, like device 30, voicerecognition from audible signals transmitted by phone 80 are providedfrom voice browser 216 to recognition server 204, either through thenetwork 205, or through a dedicated line 207, for example, using TCP/IP.Web server 202, recognition server 204 and telephone voice browser 212can be embodied in any suitable computing environment such as thegeneral purpose desktop computer illustrated in FIG. 3.

[0050] However, it should be noted that if DTMF recognition is employed,this form of recognition would generally be performed at the mediaserver 214, rather than at the recognition server 204. In other words,the DTMF grammar would be used by the media server 214.

[0051] Referring back to FIG. 4, web server 202 can include a serverside plug-in authoring tool or module 209 (e.g. ASP, ASP+, ASP.Net byMicrosoft Corporation, JSP, Javabeans, or the like). Server side plug-inmodule 209 can dynamically generate client-side markups and even aspecific form of markup for the type of client accessing the web server202. The client information can be provided to the web server 202 uponinitial establishment of the client/server relationship, or the webserver 202 can include modules or routines to detect the capabilities ofthe client device. In this manner, server side plug-in module 209 cangenerate a client side markup for each of the voice recognitionscenarios, i.e. voice only through phone 80 or multimodal for device 30.By using a consistent client side model, application authoring for manydifferent clients is significantly easier.

[0052] In addition to dynamically generating client side markups,high-level dialog modules, discussed below, can be implemented as aserver-side control stored in store 211 for use by developers inapplication authoring. In general, the high-level dialog modules 211would generate dynamically client-side markup and script in bothvoice-only and multimodal scenarios based on parameters specified bydevelopers. The high-level dialog modules 211 can include parameters togenerate client-side markups to fit the developers' needs.

Exemplary Client Side Extensions

[0053] Before describing dynamic generation of client-side markups towhich the present invention is directed, it may be helpful to firstdiscuss an exemplary form of extensions to the markup language for usein web based recognition.

[0054] As indicated above, the markup languages such as HTML, XHTMLcHTML, XML, WML or any other SGML-derived markup, which are used forinteraction between the web server 202 and the client device 30, areextended to include controls and/or objects that provide recognition ina client/server architecture. Generally, controls and/or objects caninclude one or more of the following functions: recognizer controlsand/or objects for recognizer configuration, recognizer execution and/orpost-processing; synthesizer controls and/or objects for synthesizerconfiguration and prompt playing; grammar controls and/or objects forspecifying input grammar resources; and/or binding controls and/orobjects for processing recognition results. The extensions are designedto be a lightweight markup layer, which adds the power of an audible,visual, handwriting, etc. interface to existing markup languages. Assuch, the extensions can remain independent of: the high-level page inwhich they are contained, e.g. HTML; the low-level formats which theextensions used to refer to linguistic resources, e.g. thetext-to-speech and grammar formats; and the individual properties of therecognition and speech synthesis platforms used in the recognitionserver 204. Although speech recognition will be discussed below, itshould be understood that the techniques, tags and server side controlsdescribed hereinafter can be similarly applied in handwritingrecognition, gesture recognition and image recognition.

[0055] In the exemplary embodiment, the extensions (also commonly knownas “tags”) are a small set of XML elements, with associated attributesand DOM object properties, events and methods, which may be used inconjunction with a source markup document to apply a recognition and/oraudible prompting interface, DTMF or call control to a source page. Theextensions' formalities and semantics are independent of the nature ofthe source document, so the extensions can be used equally effectivelywithin HTML, XHTML, cHTML, XML, WML, or with any other SGML-derivedmarkup. The extensions follow the document object model wherein newfunctional objects or elements, which can be hierarchical, are provided.Each of the elements are discussed in detail in the Appendix, butgenerally the elements can include attributes, properties, methods,events and/or other “child” elements.

[0056] At this point, it should also be noted that the extensions may beinterpreted in two different “modes” according to the capabilities ofthe device upon which the browser is being executed on. In a first mode,“object mode”, the full capabilities are available. The programmaticmanipulation of the extensions by an application is performed bywhatever mechanisms are enabled by the browser on the device, e.g. aJScript interpreter in an XHTML browser, or a WMLScript interpreter in aWML browser. For this reason, only a small set of core properties andmethods of the extensions need to be defined, and these manipulated bywhatever programmatic mechanisms exist on the device or client side. Theobject mode provides eventing and scripting and can offer greaterfunctionality to give the dialog author a much finer client-side controlover speech interactions. As used herein, a browser that supports fullevent and scripting is called an “uplevel browser”. This form of abrowser will support all the attributes, properties, methods and eventsof the extensions. Uplevel browsers are commonly found on devices withgreater processing capabilities.

[0057] The extensions can also be supported in a “declarative mode”. Asused herein, a browser operating in a declarative mode is called a“downlevel browser” and does not support full eventing and scriptingcapabilities. Rather, this form of browser will support the declarativeaspects of a given extension (i.e. the core element and attributes), butnot all the DOM (document object model) object properties, methods andevents. This mode employs exclusively declarative syntax, and mayfurther be used in conjunction with declarative multimediasynchronization and coordination mechanisms (synchronized markuplanguage) such as SMIL (Synchronized Multimedia Integration Language)2.0. Downlevel browsers will typically be found on devices with limitedprocessing capabilities.

[0058] At this point though, a particular mode of entry should bediscussed. In particular, use of speech recognition in conjunction withat least a display and, in a further embodiment, a pointing device aswell which enables the coordination of multiple modes of input, e.g. toindicate the fields for data entry, is particularly useful.Specifically, in this mode of data entry, the user is generally able tocoordinate the actions of the pointing device with the speech input, sofor example the user is under control of when to select a field andprovide corresponding information relevant to the field. For instance, acredit card submission graphical user interface (GUI) is illustrated inFIG. 5, a user could first decide to enter the credit card number infield 252 and then enter the type of credit card in field 250 followedby the expiration date in field 254. Likewise, the user could returnback to field 252 and correct an errant entry, if desired. When combinedwith speech recognition, an easy and natural form of navigation isprovided. As used herein, this form of entry using both a screen displayallowing free form actions of the pointing device on the screen, e.g.the selection of fields and recognition is called “multimodal”.

[0059] Referring to FIG. 6, a HTML markup language code is illustrated.The HTML code includes a body portion 270 and a script portion 272.Entry of information in each of the fields 250, 252 and 254 iscontrolled or executed by code portions 280, 282 and 284, respectively.Referring first to code portion 280, on selection of field 250, forexample, by use of stylus 33 of device 30, the event “onclick” isinitiated which calls or executes function “talk” in script portion 272.This action activates a grammar used for speech recognition that isassociated with the type of data generally expected in field 250. Thistype of interaction, which involves more than one technique of input(e.g. voice and pen-click/roller) is referred as “multimodal”.

[0060] Referring now back to the grammar, the grammar is a syntacticgrammar such as but not limited to a context-free grammar, a N-grammaror a hybrid grammar. (Of course, DTMF grammars, handwriting grammars,gesture grammars and image grammars would be used when correspondingforms of recognition are employed. As used herein, a “grammar” includesinformation for performing recognition, and in a further embodiment,information corresponding to expected input to be entered, for example,in a specific field.) A control 290 (herein identified as “reco”)includes various elements, two of which are illustrated, namely agrammar element “grammar” and a “bind” element. Generally, like the codedownloaded to a client from web server 202, the grammars can originateat web server 202 and be downloaded to the client and/or forwarded to aremote server for speech processing. The grammars can then be storedlocally thereon in a cache. Eventually, the grammars are provided to therecognition server 204 for use in recognition. The grammar element isused to specify grammars, either inline or referenced using anattribute.

[0061] Upon receipt of recognition results from recognition server 204corresponding to the recognized speech, handwriting, gesture, image,etc., syntax of reco control 290 is provided to receive thecorresponding results and associate it with the corresponding field,which can include rendering of the text therein on display 34. In theillustrated embodiment, upon completion of speech recognition with theresult sent back to the client, it deactivates the reco object andassociates the recognized text with the corresponding field. Portions282 and 284 operate similarly wherein unique reco objects and grammarsare called for each of the fields 252 and 254 and upon receipt of therecognized text is associated with each of the fields 252 and 254. Withrespect to receipt of the card number field 252, the function “handle”checks the length of the card number with respect to the card type.

Generation of Client Side Markups

[0062] As indicated above, server side plug-in module 209 outputs clientside markups when a request has been made from the client device 30. Inshort, the server side plug-in module 209 allows the website, and thus,the application and services provided by the application to be definedor constructed. The instructions in the server side plug-in module 209are made of a complied code. The code is run when a web request reachesthe web server 202. The server side plug-in module 209 then outputs anew client side markup page that is sent to the client device 30. As iswell known, this process is commonly referred to as rendering. Theserver side plug-in module 209 operates on “controls” that abstract andencapsulate the markup language, and thus, the code of the client sidemarkup page. Such controls that abstract and encapsulate the markuplanguage and operate on the webserver 202 include or are equivalent to“Servlets” or “Server-side plug ins” to name a few.

[0063] As is known, server side plug-in modules of the prior art cangenerate client side markup for visual rendering and interaction withthe client device 30. Three different approaches are provided herein forextending the server side plug-in module 209 to include recognition andaudible prompting extensions such as the exemplary client sideextensions discussed above. In a first approach illustratedschematically in FIG. 7, the current, visual, server side controls(which include parameters for visual display such as location forrendering, font, foreground color, background color, etc.) are extendedto include parameters or attributes for recognition and audiblyprompting for related recognition. Using speech recognition andassociated audible prompting by way of example, the attributes generallypertain to audible prompting parameters such as whether the promptcomprises inline text for text-to-speech conversion, playing of aprerecorded audio file (e.g. a wave file), the location of the data(text for text-to-speech conversion or a prerecorded audio file) foraudible rendering, etc. For recognition, the parameters or attributescan include the location of the grammar to be used during recognition,confidence level thresholds, etc. Since the server side plug-in module209 generates client side markup, the parameters and attributes for thecontrols for the server side plug-in module 209 relate to the extensionsprovided in the client side markup for recognition and/or audibleprompting.

[0064] The controls indicated at 300A in FIG. 7 are controls, which arewell-known in website application development or authoring tools such asASP, ASP+, ASP.Net, JSP, Javabeans, or the like. Such controls arecommonly formed in a library and used by controls 302 to perform aparticular visual task. Library 300A includes methods for generating thedesired client markup, event handlers, etc. Examples of visual controls302 include a “Label” control that provides a selected text label on avisual display such as the label “Credit Card Submission” 304 in FIG. 5.Another example of a higher level visual control 302 is a “Textbox”,which allows data to be entered in a data field such as is indicated at250 in FIG. 5. The existing visual controls 302 are also well-known. Inthe first approach for extending server side plug-in module controls toinclude recognition and/or audible prompting, each of the visualcontrols 302 would include further parameters or attributes related torecognition or audible prompting. In the case of the “label” control,which otherwise provides selected text on a visual display, furtherattributes may include whether an audio data file will be rendered ortext-to-speech conversion will be employed as well as the location ofthis data file. A library 300B, similar to library 300A, includesfurther markup information for performing recognition and/or audibleprompting. Each of the visual controls 302 is coded so as to providethis information to the controls 300B as appropriate to perform theparticular task related to recognition or audible prompting.

[0065] As another example, the “Textbox” control, which generates aninput field on a visual display and allows the user of the client device30 to enter information, would also include appropriate recognition oraudible prompting parameters or attributes such as the grammar to beused for recognition. It should be noted that the recognition or audibleprompting parameters are optional and need not be used if recognition oraudible prompting is not otherwise desired.

[0066] In general, if a control at level 302 includes parameters thatpertain to visual aspects, the control will access and use the library300A. Likewise, if the control includes parameters pertaining torecognition and/or audible prompting the control will access or use thelibrary 300B. It should be noted that libraries 300A and 300B have beenillustrated separately in order to emphasize the additional informationpresent in library 300B and that a single library having the informationof libraries 300A and 300B can be implemented.

[0067] In this approach, each of the current or prior art visualcontrols 302 are extended to include appropriate recognition/audibleprompting attributes. The controls 302 can be formed in a library. Theserver side plug-in module 209 accesses the library for markupinformation. Execution of the controls generates a client side markuppage, or a portion thereof, with the provided parameters.

[0068] In a second approach illustrated in FIG. 8, new visual,recognition/audible prompting controls 304 are provided such that thecontrols 304 are a subclass relative to visual controls 302, whereinrecognition/audible prompting functionality or markup information isprovided at controls 304. In other words, a new set of controls 304 areprovided for recognition/audible prompting and include appropriateparameters or attributes to perform the desired recognition or anaudible prompting related to a recognition task on the client device 30.The controls 304 use the existing visual controls 302 to the extent thatvisual information is rendered or obtained through a display. Forinstance, a control “SpeechLabel” at level 304 uses the “Label” controlat level 302 to provide an audible rendering and/or visual textrendering. Likewise, a “SpeechTextbox” control would associate a grammarand related recognition resources and processing with an input field.Like the first approach, the attributes for controls 304 include wherethe grammar is located for recognition, the inline text fortext-to-speech conversion, or the location of a prerecorded audio datafile that will be rendered directly or a text file throughtext-to-speech conversion. The second approach is advantageous in thatinteractions of the recognition controls 304 with the visual controls302 are through parameters or attributes, and thus, changes in thevisual controls 302 may not require any changes in the recognitioncontrols 304 provided the parameters or attributes interfacing betweenthe controls 304 and 302 are still appropriate. However, with thecreation of further visual controls 302, a correspondingrecognition/audible prompting control at level 304 may also have to bewritten.

[0069] A third approach is illustrated in FIG. 9. Generally, controls306 of the third approach are separate from the visual controls 302, butare associated selectively therewith as discussed below. In this manner,the controls 306 do not directly build upon the visual controls 302, butrather provide recognition/audible prompting enablement without havingto rewrite the visual controls 302. The controls 306, like the controls302, use a library 300. In this embodiment, library 300 includes bothvisual and recognition/audible prompting markup information and as suchis a combination of libraries 300A and 300B of FIG. 7.

[0070] There are significant advantages to this third approach. Firstly,the visual controls 302 do not need to be changed in content. Secondly,the controls 306 can form a single module which is consistent and doesnot need to change according to the nature of the speech-enabled control302. Thirdly, the process of speech enablement, that is, the explicitassociation of the controls 306 with the visual controls 302 is fullyunder the developer's control at design time, since it is an explicitand selective process. This also makes it possible for the markuplanguage of the visual controls to receive input values from multiplesources such as through recognition provided by the markup languagegenerated by controls 306, or through a conventional input device suchas a keyboard. In short, the controls 306 can be added to an existingapplication authoring page of a visual authoring page of the server sideplug-in module 209. The controls 306 provide a new modality ofinteraction (i.e. recognition and/or audible prompting) for the user ofthe client device 30, while reusing the visual controls' applicationlogic and visual input/output capabilities. In view that the controls306 can be associated with the visual controls 302 whereat theapplication logic can be coded, controls 306 may be hereinafter referredto as “companion controls 306” and the visual controls 302 be referredto as “primary controls 302”. It should be noted that these referencesare provided for purposes of distinguishing controls 302 and 306 and arenot intended to be limiting. For instance, the companion controls 306could be used to develop or author a website that does not includevisual renderings such as a voice-only website. In such a case, certainapplication logic could be embodied in the companion control logic.

[0071] A first exemplary set of companion controls 306 are furtherillustrated in FIG. 10. The set of companion controls 306 can be groupedas output controls 308 and input controls 310. Output controls 308provide “prompting” client side markups, which typically involves theplaying of a prerecorded audio file, or text for text-to-speechconversion, the data included in the markup directly or referenced via aURL. Although a single output control can be defined with parameters tohandle all audible prompting, and thus should be considered as a furtheraspect of the present invention, in the exemplary embodiment, the formsor types of audible prompting in a human dialog are formed as separatecontrols. In particular, the output controls 308 can include a“Question” control 308A, a “Confirmation” control 308B and a “Statement”control 308C, which will be discussed in detail below. Likewise, theinput controls 310 can also form or follow human dialog and include a“Answer” control 310A and a “Command” control 310B. The input controls310 are discussed below, but generally the input controls 310 associatea grammar with expected or possible input from the user of the clientdevice 30.

[0072] Although the question control 308A, confirmation control 308B,statement control 308C, answer control 310A, command control 310B, othercontrols as well as the general structure of these controls, theparameters and event handlers, are specifically discussed with respectto use as companion controls 306, it should be understood that thesecontrols, the general structure, parameters and event handlers can beadapted to provide recognition and/or audible prompting in the other twoapproaches discussed above with respect to FIGS. 7 and 8. For instance,the parameter “ClientToSpeechEnable”, which comprises one exemplarymechanism to form the association between a companion control and avisual control, would not be needed when embodied in the approaches ofFIGS. 7 and 8.

[0073] In a multimodal application, at least one of the output controls308 or one of the input controls 310 is associated with a primary orvisual control 302. In the embodiment illustrated, the output controls308 and input controls 310 are arranged or organized under a“Question/Answer” (hereinafter also “QA”) control 320. QA control 320 isexecuted on the web server 202, which means it is defined on theapplication development web page held on the web server using theserver-side markup formalism (ASP, JSP or the like), but is output as adifferent form of markup to the client device 30. Although illustratedin FIG. 10 where the QA control appears to be formed of all of theoutput controls 308 and the input controls 310, it should be understoodthat these are merely options wherein one or more may be included for aQA control.

[0074] At this point it may be helpful to explain use of the controls308 and 310 in terms of application scenarios. Referring to FIG. 11 andin a voice-only application QA control 320 could comprise a singlequestion control 308A and an answer control 310A. The question control308A contains one or more prompt objects or controls 322, while theanswer control 310A can define a grammar through grammar object orcontrol 324 for recognition of the input data and related processing onthat input. Line 326 represents the association of the QA control 320with the corresponding primary control 302, if used. In a multimodalscenario, where the user of the client device 30 may touch on the visualtextbox, for example with a “TapEvent”, an audible prompt may not benecessary. For example, for a primary control comprising a textboxhaving visual text forming an indication of what the user of clientdevice should enter in the corresponding field, a corresponding QAcontrol 320 may or may not have a corresponding prompt such as an audioplayback or a text-to-speech conversion, but would have a grammarcorresponding to the expected value for recognition, and event handlers328 to process the input, or process other recognizer events such as nospeech detected, speech not recognized, or events fired on timeouts (asillustrated in “Eventing” below).

[0075] In general, the QA control through the output controls 308 andinput controls 310 and additional logic can perform one or more of thefollowing: provide output audible prompting, collect input data, performconfidence validation of the input result, allow additional types ofinput such as “help” commands, or commands that allow the user of theclient device to navigate to other selected areas of the website, allowconfirmation of input data and control of dialog flow at the website, toname a few. In short, the QA control 320 contains all the controlsrelated to a specific topic. In this manner, a dialog is created throughuse of the controls with respect to the topic in order to inform toobtain information, to confirm validity, or to repair a dialog or changethe topic of conversation.

[0076] In one method of development, the application developer candefine the visual layout of the application using the visual controls302. The application developer can then define the spoken interface ofthe application using companion controls 306 (embodied as QA control320, or output controls 308 and input control 310). As illustrated inFIGS. 10 and 11, each of the companion controls 306 are then linked orotherwise associated with the corresponding primary or visual control302 to provide recognition and audible prompting. Of course if desired,the application developer can define or encode the application byswitching between visual controls 302 and companion controls 306,forming the links therebetween, until the application is completelydefined or encoded.

[0077] At this point, it may be helpful to provide a short descriptionof each of the output controls 308 and input controls 310. Detaileddescriptions are provided below for this embodiment in Appendix B.

[0078] Questions, Answers and Commands

[0079] Generally, as indicated above, the question controls 308A andanswer controls 310A in a QA control 320 hold the prompt and grammarresources relevant to the primary control 302, and related binding(associating recognition results with input fields of the client-sidemarkup page) and processing logic. The presence, or not, of questioncontrols 308A and answer controls 310A determines whether speech outputor recognition input is enabled on activation. Command controls 310B anduser initiative answers are activated by specification of the Scopeproperty on the answer controls 310A and command controls 310B.

[0080] In simple voice-only applications, a QA control 320 willtypically hold one question control or object 308A and one answercontrol or object 310A. Although not shown in the example below, commandcontrols 310B may also be specified, e.g. Help, Repeat, Cancel, etc., toenable user input which does not directly relate to the answering of aparticular question.

[0081] A typical ‘regular’ QA control for voice-only dialog is asfollows: <Speech:QA   id=“QA_WhichOne”  ControlsToSpeechEnable=“textBox1”   runat=“server” >   <Question >      <prompt> Which one do you want? </prompt>     </Question>    <Answer >       <grammar src=“whichOne.gram” />     </Answer>  </Speech:QA>

[0082] (The examples provided herein are written in the ASP.Netframework by example only and should not be considered as limiting thepresent invention.)

[0083] In this example, the QA control can be identified by its “id”,while the association of the QA control with the desired primary orvisual control is obtained through the parameter“ControlsToSpeechEnable”, which identifies one or more primary controlsby their respective identifiers. If desired, other well-known techniquescan be used to form the association. For instance, direct, implicitassociations are available through the first and second approachesdescribed above, or separate tables can be created used to maintain theassociations. The parameter “runat” instructs the web server that thiscode should be executed at the webserver 202 to generate the correctmarkup.

[0084] A QA control might also hold only a statement control 308C, inwhich case it is a prompt-only control without active grammars (e.g. fora welcome prompt). Similarly a QA control might hold only an answercontrol 310A, in which case it may be a multimodal control, whose answercontrol 310A activates its grammars directly as the result of an eventfrom the GUI, or a scoped mechanism (discussed below) for userinitiative.

[0085] It should also be noted that a QA control 320 may also holdmultiple output controls 308 and input controls 310 such as multiplequestion controls 308A and multiple answers controls 310A. This allowsan author to describe interactional flow about the same entity withinthe same QA control. This is particularly useful for more complexvoice-only dialogs. So a mini-dialog which may involve different kindsof question and answer (e.g. asking, confirming, giving help, etc.), canbe specified within the wrapper of the QA control associated with thevisual control which represents the dialog entity. A complex QA controlis illustrated in FIG. 11.

[0086] The foregoing represent the main features of the QA control. Eachfeature is described from a functional perspective below.

[0087] Answer Control

[0088] The answer control 310A abstracts the notion of grammars, bindingand other recognition processing into a single object or control. Answercontrols 310A can be used to specify a set of possible grammars relevantto a question, along with binding declarations and relevant scripts.Answer controls for multimodal applications such as “Tap-and-Talk” areactivated and deactivated by GUI browser events. The following exampleillustrates an answer control 310A used in a multimodal application toselect a departure city on the “mouseDown” event of the textbox“txtDepCity”, and write its value into the primary textbox control:<Speech:QA    controlsToSpeechEnable=“txtDepCity” runat=“server”> <Answer  id=“AnsDepCity”     StartEvent=“onMouseDown”    StopEvent=“onMouseUp”     />    <grammarsrc=“/grammars/depCities.gram”/>    <bind value=“//sml/DepCity”targetElement=“txtCity” />  </Answer> </Speech:QA>

[0089] Typical answer controls 310A in voice-only applications areactivated directly by question controls 308A as described below.

[0090] The answer control further includes a mechanism to associate areceived result with the primary controls. Herein, binding places thevalues in the primary controls; however, in another embodiment theassociation mechanism may allow the primary control to look at orotherwise access the recognized results.

[0091] Question Control

[0092] Question controls 308A abstracts the notion of the prompt tags(Appendix A) into an object which contains a selection of possibleprompts and the answer controls 310A which are considered responses tothe question. Each question control 308A is able to specify which answercontrol 310A it activates on its execution. This permits appropriateresponse grammars to be bundled into answer controls 310A, which reflectrelevant question controls 308A.

[0093] The following question control 308A might be used in a voice-onlyapplication to ask for a Departure City: <Speech:QA id=“QADepCity”  controlsToSpeechEnable=“txtDepCity”   runat=“server” >  <Questionid=“Q1” Answers=“AnsDepCity” >   <prompt>     Please give me thedeparture   city.   </prompt>  </Question>  <Answer id=“AnsDepCity” .../> </Speech:QA>

[0094] In the example below, different prompts can be called dependingon an internal condition of the question control 308A. The ability tospecify conditional tests on the prompts inside a question control 308Ameans that changes in wording can be accommodated within the samefunctional unit of the question control 308A. <Speech:QA  id=“QADepCity”    controlsToSpeechEnable=“txtDepCity”     runat=“server” >   <Questionid=“Q1” Answers=“AnsDepCity” >     <prompt count=“1”>       Now I needto get the departure city.       Where would you like to fly from?    </prompt>     <prompt count=“2”>       Which departure city?    </prompt>   </Question>   <Answer id=“AnsDepCity” ... /></Speech:QA>

[0095] Conditional QA Control

[0096] The following example illustrates how to determine whether or notto activate a QA control based upon information known to theapplication. The example is a portion of a survey application. Thesurvey is gathering information from employees regarding the mode oftransportation they use to get to work.

[0097] The portion of the survey first asks whether or not the userrides the bus to work. If the answer is:

[0098] Yes, the next question asks how many days last week the usersrode the bus.

[0099] No, the “number of days rode the bus” question is bypassed.<asp:Label id=“lblDisplay1”       text=“Do you ride the bus to work?”      runat=“server”/> <asp:DropDownList id=“lstRodeBusYN”runat=“server”>     <asp:ListItem selected=“true”>No</asp:ListItem>    <asp:ListItem>Yes</asp:ListItem> </asp:DropDownList> <Speech:QAid=“QA_RideBus     ControlsToSpeechEnable=“lstRodeBusYN”    runat=“server” >   <SDN:Question id=“Q_RideBus” >     <promptbargeIn=“False”>     Do you ride the bus to work?     </prompt>  </SDN:Question>   <SDN:Answer id=“A_RideBus”         autobind=“False”        StartEvent=“onMouseDown”         StopEvent=“onMouseUp”        runat=“server”   onClientReco=“ProcessRideBusAnswer”    <grammar src=“...” /> <--! “yes/no” grammar -->   </SDN:Answer></Speech:QA> <asp:Label id=“lblDisplay2”     enabled=“False”    text=“How many days last week did you ride   the bus to work?”    runat=“server”/> <asp:DropDownList id=“lstDaysRodeBus”enabled=“False” runat=“server”>     <asp:ListItemselected=“true” >0</asp:ListItem>     <asp:ListItem>1</asp:ListItem>    <asp:ListItem>2</asp:ListItem>     <asp:ListItem>3</asp:ListItem>    <asp:ListItem>4</asp:ListItem>     <asp:ListItem>5</asp:ListItem>    <asp:ListItem>6</asp:ListItem>     <asp:ListItem>7</asp:ListItem>   </asp:DropDownList> <Speech:QA id=“QA_DaysRodeBus”     ControlsToSpeechEnable=“lstDaysRodeBus”     ClientTest=“RideBusCheck”      runat=“server” >   <Questionid=“Q_DaysRodeBus” >   <prompt bargeIn=“False”>     How many days lastweek did you ride the bus to work?     </prompt>   </SDN:Question>  <SDN:Answer id=“A_DaysRodeBus”         autobind=“False”        StartEvent=“onMouseDown”         StopEvent=“onMouseUp”        runat=“server”   onClientReco=“ProcessDaysRodeBusAnswer”    <grammar src=“...” /> <--! “numbers” grammar -->   </SDN:Answer></Speech:QA> <script language=“jscript”>   functionProcessRideBusAnswer( ) {    <--! using SML attribute of the Eventobject, determine yes or no answer -->    <--! then select theappropriate item in the dropdown listbox -->    <--! and enable the nextlabel and dropdown listbox if answer is “yes” -->    if <--! Answer is“yes” --> {     lstRodeBusYN.selectedIndex=2    lblDisplay2.enabled=“true”     lstDaysRodeBus.enabled=“true” }   }  function RideBusCheck( ) {     if lstRodeBusYN.selectedIndex=“1” <--!this is no -->       then return “False”     endif   }   functionProcessDaysRodeBusAnswer( ) {     <--! case statement to select properdropdown item -->   } </script>

[0100] In the example provided above, the QA control “QA_DaysRodeBus” isexecuted based on a boolean parameter “ClientTest”, which in thisexample, is set based on the function RideBusCheck( ). If the functionreturns a false condition, the QA control is not activated, whereas if atrue condition is returned the QA control is activated. The use of anactivation mechanism allows increased flexibility and improved dialogflow in the client side markup page produced. As indicated in Appendix Bmany of the controls and objects include an activation mechanism.

[0101] Command Control

[0102] Command controls 310B are user utterances common in voice-onlydialogs which typically have little semantic import in terms of thequestion asked, but rather seek assistance or effect navigation, e.g.help, cancel, repeat, etc. The Command control 310B within a QA control306 can be used to specify not only the grammar and associatedprocessing on recognition (rather like an answer control 310A withoutbinding of the result to an input field), but also a ‘scope’ of contextand a type. This allows for the authoring of both global andcontext-sensitive behavior on the client side markup.

[0103] As appreciated by those skilled in the art from the foregoingdescription, controls 306 can be organized in a tree structure similarto that used in visual controls 302. Since each of the controls 306 arealso associated with selected visual controls 302, the organization ofthe controls 306 can be related to the structure of the controls 302.

[0104] The QA controls 302 may be used to speech-enable both atomiccontrols (textbox, label, etc.) and container controls (form, panel,etc.) This provides a way of scoping behaviour and of obtainingmodularity of subdialog controls. For example, the scope will allow theuser of the client device to navigate to other portions of the clientside markup page without completing a dialog.

[0105] In one embodiment, “Scope” is determined as a node of the primarycontrols tree. The following is an example “help” command, scoped at thelevel of the “Pnl1” container control, which contains two textboxes.<asp:panel id=“Pnl1” ...>   <asp:textbox id=“tb1” ... />   <asp:textboxid=“tb2” ... /> </asp:panel> <Speech:QA ... >   <Command   id=“HelpCmd1”    scope=“Pnl1”    type=“help”   onClientReco=“GlobalGiveHelp( )” >    <Grammarsrc=“grammars/help.gram”/>   </Command>  </Speech:QA> <script>   function GlobalGiveHelp( ) {       ...    } </script>

[0106] As specified, the “help” grammar will be active in every QAcontrol relating to “Pnl1” and its contents. The GlobalGiveHelpsubroutine will execute every time “help” is recognized. To overridethis and achieve context-sensitive behavior, the same typed command canbe scoped to the required level of context: <Speech:QA ... >   <Command   id=“HelpCmd2”    scope=“Tb2”    type=“help”   onClientReco=“SpecialGiveHelp( )” >    <Grammarsrc=“grammars/help.gram”/>   </Command> </Speech:QA> <script>   function SpecialGiveHelp( ) {      ...    } </script>

[0107] Confirmation Control

[0108] The QA control 320 can also include a method for simplifying theauthoring of common confirmation subdialogs. The following QA controlexemplifies a typical subdialog which asks and then confirms a value:<Speech:QA   id=“qaDepCity”   controlsToSpeechEnable=“txtDepCity”  runat=“server” >   <!-- asking for a value -->  <Question    id=“AskDepCity”       type=“ask”      Answers=“AnsDepCity” >     <prompt> Which city? </prompt>  </Question>   <Answer  id=“AnsDepCity”         confirmThreshold=“60” >    <grammar src=“grammars/depCity.gram”   />   </Answer>   <!--confirming the value -->   <Confirm id=“ConfirmDepCity”      Answers=“AnsConfDepCity” >     <prompt>       Did you say <value    targetElement=“txtDepCity/Text”>?     </prompt>   </Confirm>  <Answer  id=“AnsConfDepCity” >     <grammar  src=“grammars/YesNoDepCity.gram” />   </Answer> </Speech:QA>

[0109] In this example, a user response to ‘which city?’ which matchesthe AnsDepCity grammar but whose confidence level does not exceed theconfirmThreshold value will trigger the confirm control 308. Moreflexible methods of confirmation available to the author includemechanisms using multiple question controls and multiple answercontrols.

[0110] In a further embodiment, additional input controls related to theconfirmation control include an accept control, a deny control and acorrect control. Each of these controls could be activated (in a mannersimilar to the other controls) by the corresponding confirmation controland include grammars to accept, deny or correct results, respectively.For instance, users are likely to deny be saying “no”, to accept bysaying “yes” or “yes+current value” (e.g., “Do you want to go toSeattle?” “Yes, to Seattle”), to correct by saying “no”+new value (e.g.,“Do you want to go to Seattle” “No, Pittsburgh”).

[0111] Statement Control

[0112] The statement control allows the application developer to providean output upon execution of the client side markup when a response isnot required from the user of the client device 30. An example could bea “Welcome” prompt played at the beginning of execution of a client sidemarkup page.

[0113] An attribute can be provided in the statement control todistinguish different types of information to be provided to the user ofthe client device. For instance, attributes can be provided to denote awarning message or a help message. These types could have differentbuilt-in properties such as different voices. If desired, differentforms of statement controls can be provided, i.e. a help control,warning control, etc. Whether provided as separate controls orattributes of the statement control, the different types of statementshave different roles in the dialog created, but share the fundamentalrole of providing information to the user of the client device withoutexpecting an answer back.

[0114] Eventing

[0115] Event handlers as indicated in FIG. 11 are provided in the QAcontrol 320, the output controls 308 and the input controls 310 foractions/inactions of the user of the client device 30 and for operationof the recognition server 204 to name a few, other events are specifiedin Appendix B. For instance, mumbling, where the speech recognizerdetects that the user has spoken but is unable to recognize the wordsand silence, where speech is not detected at all, are specified in theQA control 320. These events reference client-side script functionsdefined by the author. In a multimodal application specified earlier, asimple mumble handler that puts an error message in the text box couldbe written as follows:   <Speech:QA        controlsToSpeechEnable=“txtDepCity”        onClientNoReco=“OnMumble( )”       runat=“server”>     <Answerid=“AnsDepCity”       StartEvent=“onMouseDown”      StopEvent=“onMouseUp”       >     <grammarsrc=“/grammars/depCities.gram”/>     <bind value=“//sml/DepCity”  targetElement=“txtCity” />    </Answer>   </Speech:QA>   <script>    function OnMumble( ) {       txtDepCity.value=“...recognitionerror...”;     }   </script>

[0116] Control Execution Algorithm

[0117] In one embodiment, a client-side script or module (hereinreferred to as “RunSpeech”) is provided to the client device. Thepurpose of this script is to execute dialog flow via logic, which isspecified in the script when executed on the client device 30, i.e. whenthe markup pertaining to the controls is activated for execution on theclient due to values contained therein. The script allows multipledialog turns between page requests, and therefore, is particularlyhelpful for control of voice-only dialogs such as through telephonybrowser 216. The client-side script RunSpeech is executed in a loopmanner on the client device 30 until a completed form in submitted, or anew page is otherwise requested from the client device 30.

[0118] It should be noted that in one embodiment, the controls canactivate each other (e.g. question control activating a selected answercontrol) due to values when executed on the client. However, in afurther embodiment, the controls can “activate” each other in order togenerate appropriate markup, in which case server-side processing may beimplemented.

[0119] Generally, in one embodiment, the algorithm generates a dialogturn by outputting speech and recognizing user input. The overall logicof the algorithm is as follows for a voice-only scenario:

[0120] 1. Find next active output companion control;

[0121] 2. If it is a statement, play the statement and go back to 1; Ifit is a question or a confirm go to 3;

[0122] 3. Collect expected answers;

[0123] 4. Collect commands;

[0124] 5. Play output control and listen in for input;

[0125] 6. Activate recognized Answer or Command object or, issue anevent if none is recognized;

[0126] 7. Go back to 1.

[0127] In the multimodal case, the logic is simplified to the followingalgorithm:

[0128] 1. Wait for triggering event—i.e., user tapping on a control;

[0129] 2. Collect expected answers;

[0130] 3. Listen in for input;

[0131] 4. Activate recognized Answer object or, if none, throw event;

[0132] 5. Go back to 1.

[0133] The algorithm is relatively simple because, as noted above,controls contain built-in information about when they can be activated.The algorithm also makes use of the role of the controls in thedialogue. For example statements are played immediately, while questionsand confirmations are only played once the expected answers have beencollected.

[0134] In a further embodiment, implicit confirmation can be providedwhereby the system confirms a piece of information and asks a questionat the same time. For example the system could confirm the arrival cityof a flight and ask for the travel date in one utterance: “When do youwant to go to Seattle?” (i.e. asking ‘when’ and implicitly confirming‘destination: Seattle’). If the user gives a date then the city isconsidered implicitly accepted since, if the city was wrong, users wouldhave immediately challenged it. In this scenario, it becomes clear thatthe knowledge of what a user is trying to achieve is vitally important:are they answering the question, or are they correcting the value, orare they asking for help? By using the role of the user input in thedialogue the system can know when to implicitly accept a value.

[0135] In summary, a dialog is created due to the role of the control inthe dialog and the relationship with other controls, wherein thealgorithm executes the controls and thus manages the dialog. Eachcontrol contains information based on its type which is used by theexecution algorithm to select (i.e. make active for execution) a givencontrol according to whether or not it serves a useful purpose at thatpoint in the dialog on the client. For example, confirmation controlsare only active when there is a value to confirm and the system does nothave sufficient confidence in that value to proceed. In a furtherimplementation, most of these built-in pieces of information can beoverridden or otherwise adapted by application developers.

[0136] The following table summarizes the controls, their correspondingrole in the dialog and the relationship with other controls.Relationship with other Control Role in dialogue controls Statementoutput: present (none) information to users Question output: ask selectsexpected Answers question as a response Confirmation output: confirm aselects potential input value obtained from controls as a response, theuser typically Accept, Deny, Correct Answer input: provide an selectedby answer to a Question/Confirmation question Command input: seek toscoped to other controls repair a dialog, or change the topic ofconversation Accept input: confirm a selected by a value in responseconfirmation to a confirmation Deny input: deny a value selected by a inresponse to a confirmation confirmation Correct input: correct aselected by a value in response confirmation to a confirmation QA(wrapper: contains all the controls related to a specific topic)

[0137] The use of these controls may be explained with an illustrationof a simple human/computer dialog. In the dialog below, each dialog turnon the part of the System or the User is characterized according to thecontrol (indicated in parentheses) which reflects its purpose in thedialog.

[0138] 1. System (Statement): “Welcome to the travel booking service”.

[0139] 2. System (Question): “Where would you like to go?”

[0140] 3. User (Answer): “San Francisco.”

[0141] 4. System (Confirmation): “Did you say Seattle?”

[0142] 5. User (Deny): “No.”

[0143] 6. System (Question): “Where would you like to go?”

[0144] 7. User (Answer): “San Francisco.”

[0145] 8. System (Confirmation): “Did you say Seattle?”

[0146] 9. User (Correct): “I said San Francisco.”

[0147] 10. System (Confirmation): “Did you say San Francisco?”

[0148] 11. User (Correct): “Yes.”

[0149] 12. System (Question): “When would you like to leave?”

[0150] 13. User (Command): “Help.”

[0151] Turn 1 is a statement on the part of the System. Since astatement control activates no answer controls in response, the systemdoes not expect input. The system goes on to activate a question controlat turn 2. This in turn activates a set of possible answer controls,including one which holds a grammar containing the cities availablethrough the service, including “San Francisco”, “Seattle”, etc., whichpermits the user to provide such a city in turn 3.

[0152] The user's turn 3 is misrecognized by the system. Although thesystem believes it has a value from an answer control for the city, itsconfidence in that value is low (rightly so, since it has recognizedincorrectly). This low confidence value in a just-received answercontrol is sufficient information for RunSpeech to trigger aconfirmation control on the part of the system, as generated at turn 4.The confirmation control in turn activates a deny control, a correctcontrol and an accept control and makes their respective grammarsavailable to recognize the user's next turn. User turns 5, 9 and 11illustrate example responses for these controls. Turn 5 of the usersimply denies the value “no”. This has the effect of removing the valuefrom the system, so the next action of RunSpeech is to ask the questionagain to re-obtain the value (turn 6).

[0153] Turns 7 and 8 return us to a confirmation control as with 3 and4.

[0154] User turn 9 is a correct control, which has again been activatedas a possible response to the confirmation control. A correct controlnot only denies the value undergoing confirmation, it also provides anew value. So user turn 9 is recognized by the system as a correctcontrol with a new value which, correctly this time, is recognized as“San Francisco”.

[0155] The system's confidence in the new value is low, however, and yetanother confirmation control is generated at turn 10. This in turnactivates accept, deny and correct controls in response, and user turn11 (“Yes” matches an accept control grammar. The recognition of theaccept control has the effect of ‘grounding’ the system's belief in thevalue which it is trying to obtain, and so RunSpeech is now able toselect other empty values to obtain. In turn 12, a new question controlis output which asks for a date value. The user's response this time(turn 13) is a command: “help”. Command controls are typically activatedin global fashion, that is, independently of the different questioncontrols and confirmation controls on the part of the system. In thisway the user is able to ask for help at any time, as he does in turn 13.Command controls may also be more sensitively enabled by a mechanismthat scopes their activation according to which part of the primarycontrol structure is being talked about.

[0156] Referring back to the algorithm, in one exemplary embodiment, theclient-side script RunSpeech examines the values inside each of theprimary controls and an attribute of the QA control, and any selectiontest of the QA controls on the current page, and selects a single QAcontrol for execution. For example, within the selected QA control, asingle question and its corresponding prompt are selected for output,and then a grammar is activated related to typical answers to thecorresponding question. Additional grammars may also be activated, inparallel, allowing other commands (or other answers), which areindicated as being allowable. Assuming recognition has been made and anyfurther processing on the input data is complete, the client-side scriptRunSpeech will begin again to ascertain which QA control should beexecuted next. An exemplary implementation and algorithm of RunSpeech isprovided in Appendix B.

[0157] It should be noted that the use of the controls and the RunSpeechalgorithm or module is not limited to the client/server applicationdescribed above, but rather can be adapted for use with otherapplication abstractions. For instance, an application such as VoiceXML,which runs only on the client device 30, could conceivably includefurther elements or controls such as question and answer provided aboveas part of the VoiceXML browser and operating in the same manner. Inthis case the mechanisms of the RunSpeech algorithm described abovecould be executed by default by the browser without the necessity forextra script. Similarly, other platforms such as finite state machinescan be adapted to include the controls and RunSpeech algorithm or moduleherein described.

[0158] Synchronization

[0159] As noted above, the companion controls 306 are associated withthe primary controls 302 (the existing controls on the page). As suchthe companion controls 306 can re-use the business logic andpresentation capabilities of the primary controls 302. This is done intwo ways: storing values in the primary controls 302 and notifying theprimary controls of the changes 302.

[0160] The companion controls 306 synchronize or associates their valueswith the primary controls 302 via the mechanism called binding. Bindingputs values retrieved from recognizer into the primary controls 302, forexample putting text into a textbox, herein exemplified with the answercontrol. Since primary controls 302 are responsible for visualpresentation, this provides visual feedback to the users in multimodalscenarios.

[0161] The companion controls 306 also offer a mechanism to notify theprimary controls 302 that they have received an input via therecognizer. This allows the primary controls 302 to take actions, suchas invoking the business logic. (Since the notification amounts to acommitment of the companion controls 306 to the values which they writeinto the primary controls 302, the implementation provides a mechanismto control this notification with a fine degree of control. This controlis provided by the RejectThreshold and ConfirmThreshold properties onthe answer control, which specify numerical acoustic confidence valuesbelow which the system should respectively reject or attempt to confirma value.)

[0162] A second exemplary set of companion controls 400 is illustratedin FIG. 12. In this embodiment, the companion controls 400 generallyinclude a QA control 402, a Command control 404, a CompareValidatorcontrol 406, a Custom Validator control 408 and a semantic map 410. Thesemantic map 410 schematically illustrated and includes semantic items412 that form a layer between the visual domain primary controls 402(e.g. HTML and a non-visual recognition domain of the companion controls400.

[0163] At this point, it should be emphasized that that although theorganization of the companion controls QA and Command is different thanthat of the first set of companion controls discussed above, thefunctionality remains the same. In particular, the QA control 402includes a Prompt property that references Prompt objects to perform thefunctions of output controls, i.e. that provide “prompting” client sidemarkups for human dialog, which typically involves the playing of aprerecorded audio file, or text for text-to-speech conversion, the dataincluded in the markup directly or referenced via a URL. Likewise, theinput controls are embodied as the QA control 402 and Command Control404 and also follow human dialog and include the Prompt property(referencing a Prompt object) and an Answer property that references atleast one Answer object. Both the QA control 402 and the Command control404 associate a grammar with expected or possible input from the user ofthe client device 30. The QA control 402 in this embodiment can thus beconsidered a question control, an answer control as well as a confirmcontrol and a statement control since it includes properties necessaryfor performing these functions.

[0164] Although the QA control 402, Command control 404, CompareValidator control 406 and Custom Validator control 408 and othercontrols as well as the general structure of these controls, theparameters and event handlers, are specifically discussed with respectto use as companion controls 400, it should be understood that thesecontrols, the general structure, parameters and event handlers can beadapted to provide recognition and/or audible prompting in the other twoapproaches discussed above with respect to FIGS. 7 and 8. For instance,the Semantic Map 410, which comprises another exemplary mechanism toform the association between the companion controls and visual control302, would not be needed when embodied in the approaches of FIGS. 7 and8.

[0165] At this point, it may be helpful to provide a short descriptionof each of the controls. Detailed descriptions are provided below inAppendix C.

[0166] QA Control

[0167] In general, the QA control 402 through the properties illustratedcan perform one or more of the following: provide output audibleprompting, collect input data, perform confidence validation of theinput result, allow confirmation of input data and aid in control ofdialog flow at the website, to name a few. In other words, the QAcontrol 402 contains properties that function as controls for a specifictopic.

[0168] The QA control 402, like the other controls, is executed on theweb server 202, which means it is defined on the application developmentweb page held on the web server using the server-side markup formalism(ASP, JSP or the like), but is output as a different form of markup tothe client device 30. Although illustrated in FIG. 12 where the QAcontrol appears to be formed of all of the properties Prompt, Reco,Answers, ExtraAnswers and Confirms, it should be understood that theseare merely options wherein one or more may be included for a QA control.

[0169] At this point it may be helpful to explain use of the QA controls402 in terms of application scenarios. Referring to FIG. 12 and in avoice-only application QA control 402 could function as a question andan answer in a dialog. The question would be provided by a Promptobject, while a grammar is defined through grammar object forrecognition of the input data and related processing on that input. AnAnswers property associates the recognized result with a SemanticItem412 in the Semantic Map 410 using an Answer object, which containsinformation on how to process recognition results. Line 414 representsthe association of the QA control 402 with the Semantic Map 410, and toa SemanticItem 412 therein. Many SemanticItems 412 are individuallyassociated with a visual or primary control 302 as represented by line418, although one or more SemanticItems 412 may not be associated with avisual control and used only internally. In a multimodal scenario, wherethe user of the client device 30 may touch on the visual textbox, forexample with a “TapEvent”, an audible prompt may not be necessary. Forexample, for a primary control comprising a textbox having visual textforming an indication of what the user of client device should enter inthe corresponding field, a corresponding QA control 402 may or may nothave a corresponding prompt such as an audio playback or atext-to-speech conversion, but would have a grammar corresponding to theexpected value for recognition, and event handlers to process the input,or process other recognizer events such as no speech detected, speechnot recognized, or events fired on timeouts.

[0170] In a further embodiment, the recognition result includes aconfidence level measure indicating the level of confidence that therecognized result was correct. A confirmation threshold can also bespecified in the Answer object, for example, as ConfirmThreshold equals0.7. If the confirmation level exceeds the associated threshold, theresult can be considered confirmed.

[0171] It should also be noted that in addition, or in the alternative,to specifying a grammar for speech recognition, QA controls and/orCommand controls can specify Dtmf (dual tone modulated frequency)grammars to recognize telephone key activations in response to promptsor questions. Appendix C provides details of a Dtmf object that appliesa different modality of grammar (a keypad input grammar rather than, forexample, a speech input grammar) to the same question. Some of theproperties of the Dtmf object include Preflush, which is a flagindicating if “type-ahead” functionality is allowed in order that theuser can provide answers to questions before they are asked. Otherproperties include the number of milliseconds to wait for receiving thefirst key press, InitialTimeOut, and the number of milliseconds to waitbefore adjacent key presses, InterdigitTimeOut. Client-side scriptfunctions can be specified for execution through other properties, forexample, when no key press is received, OnClientSilence, or when theinput is not recognized, OnClientNoReco, or when an error is detectedOnClientError.

[0172] At this point it should be noted that when a Semanticitem 412 ofthe Semantic map 410 is filled, through recognition for example, speechor Dtmf, several actions can be taken. First, an event can be issued orfired indicating that the value has been “changed”. Depending on if theconfirmation level was met, another event that can be issued or firedincludes a “confirm” event that indicates that the correspondingsemantic item has been confirmed. These events are used for controllingdialog.

[0173] The Confirms property can also include answer objects having thestructure similar to that described above with respect to the Answersproperty in that it is associated with a SemanticItem 412 and caninclude a ConfirmThreshold if desired. The Confirms property is notintended to obtain a recognition result per se, but rather, to confirm aresult already obtained and ascertain from the user whether the resultobtained is correct. The Confirms property is a collection of Answerobjects used to assert whether the value of a previously obtained resultwas correct. The containing QA's Prompt object will inquire about theseitems, and obtains the recognition result from the associatedSemanticItem 412 and forms it in a question such as “Did you saySeattle?” If the user responds with affirmation such as “Yes”, theconfirmed event is then fired. If the user responds in the negative suchas “No”, the associated SemanticItem 412 is cleared.

[0174] It should be noted in a further embodiment, the Confirms propertycan also accept corrections after a confirmation prompt has beenprovided to the user. For instance, in response to a confirmation prompt“Did you say Seattle?” the user may respond “San Francisco” or “No, SanFrancisco”, in which case, the QA control has received a correction.Having information as to which SemanticItem is being confirmed throughthe Answer object, the value in the SemanticItem can be replaced withthe corrected value. It should also be noted that if desired,confirmation can be included in a further prompt for information such as“When did you want to go to Seattle?”, where the prompt by the systemincludes a confirmation for “Seattle” and a further prompt for the dayof departure. A response by the user providing a correction to the placeof destination would activate the Confirms property to correct theassociated semantic item, while a response with only a day of departurewould provide implicit confirmation of the destination.

[0175] The ExtraAnswers property allows the application author tospecify Answer objects that a user may provide in addition to a promptor query that has been made. For instance, if a travel oriented systemprompts a user for a destination city, but the user responds byindicating “Seattle tomorrow”, the Answers property that initiallyprompted the user will retrieve and therefore bind the destination city“Seattle” to the appropriate SemanticItem, while the ExtraAnswersproperty can process “Tomorrow” as the next succeeding day (assumingthat the system knows the current day), and thereby, bind this result tothe appropriate SemanticItem in the Semantic Map. The ExtraAnswersproperty includes one or more Answer objects defined for possible extrainformation the user may also state. In the example provided above,having also retrieved information as to the day of departure, the systemwould then not need to reprompt the user for this information, assumingthat the confirmation level exceeded the corresponding ConfirmThreshold.If the confirmation level did not exceed the corresponding threshold,the appropriate Confirms property would be activated.

[0176] Command Control

[0177] Command controls 404 are user utterances common in voice-onlydialogs which typically have little semantic import in terms of thequestion asked, but rather seek assistance or effect navigation, e.g.help, cancel, repeat, etc. The Command control 404 can include a Promptproperty to specify a prompt object. In addition, the Command control404 can be used to specify not only the grammar (through a Grammarproperty) and associated processing on recognition (rather like anAnswer object without binding of the result to an SemanticItem), butalso a ‘scope’ of context and a type. This allows for the authoring ofboth global and context-sensitive behavior on the client side markup.The Command control 404 allows additional types of input such as “help”commands, or commands that allow the user of the client device tonavigate to other selected areas of the website.

[0178] CompareValidator Control

[0179] The CompareValidator control compares two values according to anoperator and takes an appropriate action. The values to be compared canbe of any form such as integers, strings of text, etc. TheCompareValidator includes a property SematicItemtoValidate thatindicates the SemanticItem that will be validated. The SemanticItem tobe validated can be compared to a constant or another SemanticItem,where the constant or other SemanticItem is provided by propertiesValuetoCompare and SematicItemtoCompare, respectively. Other parametersor properties associated with the CompareValidator include Operator,which defines the comparison to be made and Type, which defines the typeof value, for example, integer or string of the semantic items.

[0180] If the validation associated with the

[0181] CompareValidator control fails, a Prompt property can specify aPrompt object that can be played instructing the user that the resultobtained was incorrect. If upon comparison the validation fails, theassociated SemanticItem defined by SematicItemtoValidate is indicated asbeing empty, in order that the system will reprompt the user for acorrect value. However, it may be helpful to not clear the incorrectvalue of the associated SemanticItem in the Semantic Map in the eventthat the incorrect value will be used in a prompt to the userreiterating the incorrect value. The CompareValidator control can betriggered either when the value of the associated SemanticItem changesvalue or when the value has been confirmed, depending on the desires ofthe application author.

[0182] CustomValidator Control

[0183] The CustomValidator control is similar to the CompareValidatorcontrol. A property SematicItemtoValidate indicates the SemanticItemthat will be validated, while a property ClientValidationFunctionspecifies a custom validation routine through an associated function orscript. The function would provide a Boolean value “yes” or “no” or anequivalent thereof whether or not the validation failed. A Promptproperty can specify a Prompt object to provide indications of errors orfailure of the validation. The CustomValidator control can be triggeredeither when the value of the associated SemanticItem changes value orwhen the value has been confirmed, depending on the desires of theapplication author.

[0184] Control Execution Algorithm

[0185] As in the previous set of controls, a client-side script ormodule (herein referred to as “RunSpeech”) is provided to the clientdevice for the controls of FIG. 12. Again, the purpose of this script isto execute dialog flow via logic, which is specified in the script whenexecuted on the client device 30, i.e. when the markup pertaining to thecontrols is activated for execution on the client due to valuescontained therein. The script allows multiple dialog turns between pagerequests, and therefore, is particularly helpful for control ofvoice-only dialogs such as through telephony browser 216. Theclient-side script RunSpeech is executed in a loop manner on the clientdevice 30 until a completed form is submitted, or a new page isotherwise requested from the client device 30.

[0186] Generally, in one embodiment, the algorithm generates a dialogturn by outputting speech and recognizing user input. The overall logicof the algorithm is as follows for a voice-only scenario (reference ismade to Appendix C for properties or parameters not otherwise discussedabove):

[0187] 1. Find the first active (as defined below) QA, CompareValidatoror CustomValidator control in speech index order.

[0188] 2. If there is no active control, submit the page.

[0189] 3. Otherwise, run the control.

[0190] A QA is considered active if and only if:

[0191] 1. The QA's clientActivationFunction either is not present orreturns true, AND

[0192] 2. If the Answers property collection is non empty, the State ofall of the SemanticItems pointed to by the set of Answers is Empty OR

[0193] 3. If the Answers property collection is empty, the State atleast one SemanticItem in the Confirm array is NeedsConfirmation.

[0194] However, if the QA has PlayOnce true and its Prompt has been runsuccessfully (reached OnComplete) the QA will not be a candidate foractivation.

[0195] A QA is run as follows:

[0196] 1. If this is a different control than the previous activecontrol, reset the prompt Count value.

[0197] 2. Increment the Prompt count value

[0198] 3. If PromptSelectFunction is specified, call the function andset the Prompt's inlinePrompt to the returned string.

[0199] 4. If a Reco object is present, start it. This Reco shouldalready include any active command grammar.

[0200] A Validator (either a CompareValidator or a CustomValidator) isactive if:

[0201] 1. The SemanticItemToValidate has not been validated by thisvalidator and its value has changed.

[0202] A CompareValidator is run as follows:

[0203] 1. Compare the values of the SemanticItemToCompare orValueToCompare and SemanticItemToValidate according to the validator'sOperator.

[0204] 2. If the test returns false, empty the text field of theSemanticItemToValidate and play the prompt.

[0205] 3. If the test returns true, mark the SemanticItemToValidate asvalidated by this validator.

[0206] A CustomValidator is run as follows:

[0207] 1. The ClientValidationFunction is called with the value of theSemanticItemToValidate.

[0208] 2. If the function returns false, the semanticItem cleared andthe prompt is played, otherwise as validated by this validator.

[0209] A Command is considered active if and only if:

[0210] 1. It is in Scope, AND

[0211] 2. There is not another Command of the same Type lower in thescope tree.

[0212] In the multimodal case, the logic is simplified to the followingalgorithm:

[0213] 1. Wait for triggering event—i.e., user tapping on a control;

[0214] 2. Collect expected answers;

[0215] 3. Listen in for input;

[0216] 4. Bind result to SemanticItem, or if none, throw event;

[0217] 5. Go back to 1.

[0218] In a multi-model environment, it should be noted that if the usercorrects the text box or other input field associated with a visualpresentation of the result, the system can update the associatedSemanticItem to indicate that the value has been confirmed.

[0219] In a further embodiment, controls are provided that enableapplication authors to create speech applications that handle telephonytransactions. In general, the controls implement or invoke well-knowntelephony transactions such as ECMA (European Computer ManufacturesAssociated) CSTA (Computer Supported Telecommunication Application)messages, eventing and services. As is known, CSTA specifies applicationinterfaces and protocols for monitoring and controlling calls anddevices in a communication network. These calls and devices may supportvarious media and can reside in various network environments such as IP,Switched Circuit Networks and mobile networks.

[0220] In the illustrated embodiment, the controls available to theapplication author include a SmexMessage control (SMEX-Simple MessageExchange), a TransferCall control, a MakeCall control, a DisconnectCallcontrol and an AnswerCall control. Like the controls described above,these controls can be executed on the server so as to generateclient-side markup that when executed on the client device perform thedesired telephony transaction.

[0221] Referring to FIG. 4, the client-side markup generated by server202 can be executed by voice browser 216, which in turn providestelephony transactions instructions (e.g. CSTA service calls) to themedia server 214 and gateway 210 as necessary to perform the desiredtelephony transaction. Appendix C provides detailed informationregarding each of the properties available in the controls. The controlsare commonly used in a voice-only mode such as by voice browser 216 inFIG. 4; however, it should be understood that applications can bewritten also to be executed in an multi-modal client device.

[0222]FIG. 12 schematically illustrates the call controls at 407. Thecall controls 407 described further below are generally used inconjunction with the controls described above such as the QA control402, Command control 404 and/or validators 406 and 408 to provide audioprompting, if necessary, and perform recognition so as to performdesired telephony transactions.

[0223] The SmexMessage control allows application authors to send andreceive raw CTSA messages. Like the controls discussed above, thecall-related controls include a SpeechIndex property that controls theorder of the object within the RunSpeech algorithm. Since the number andtypes of events generated by sending a message with the SmexMessagecontrol is unknown, the application author should be careful about whenthe RunSpeech algorithm can continue.

[0224] A required property of the SmexMessage control is the CSTA XMLmessage to be sent. Optional client-side functions can be called beforethe message is sent in order to modify the message, or a client-sidefunction that is called when a SMEX object receives a SMEX event.SmexMessage control may be used to receive incoming telephone calls.

[0225] The call-related server-side controls discussed below deal with asingle device and a single active call at any given time. If theapplication author needs to monitor more than one device or handle morethan one active call, SmexMessage control can be used by the applicationauthor to provide code to handle CSTA messages.

[0226] The TransferCall control is used to transfer the current callusing CSTA SingleStepTransfer service. Required properties include adevice identifier associated with the transfer to endpoint. Otherproperties can include client-side functions to be called when the callis transferred or when CSTA returns a failed event. In addition, aserver-side event can be issued when the called is transferred.

[0227] The MakeCall control makes an outbound call to a given number ona given device when the RunSpeech algorithm runs this object. Requiredproperties include an identifier device that the control will use toplace the outbound call and the phone number to dial. The server-sideevents can be issued when a call is connected. Likewise, client-sideevents can be called when the call is connected or when the call failsas indicated by a CSTA message returning a failed event.

[0228] The DisconnectCall control allows application authors todisconnect or terminate telephone calls using CSTA ClearConnectionservice. If desired, a server-side event can be issued when the call isdisconnected and/or a client-side function can be called when the callis disconnected.

[0229] The AnswerCall control answers incoming calls on a given deviceusing CSTA AnswerCall Service. In a manner similar to the DisconnectCallcontrol discussed above, a server-side event can be issued when the callis connected, and/or a client-side function can be called when the callis connected.

[0230] From the foregoing, a method and system are provided forgenerating mark-up for client side devices for speech-enabledapplications. The same set of controls can be used in three differentforms of interaction including Voice-only, Tap-and-talk (multi-modal)and Hands-free (multi-modal). In Voice-only dialogs are provided on aGUI-less browser such as for telephony applications. This kind ofapplication is driven by a dialog-flow manager that runs on the client(RunSpeech). In Tap-and-talk multi-modal dialogs contain a usable GUIwithout speech output. System prompts are generally not provided and theinteraction is managed by the user's click events on the GUI. InHands-free multi-modal, dialogs use a GUI display and speech input andoutput. The dialog may be authored for Tap-and-talk, but may still usethe RunSpeech algorithm, or other speech controls features, to enablesystem driven voice prompting, while confirmation is provided visually.Switching between multi-modal/hands-free and voice-only is done bydetecting the type of client the controls are talking to. Generally,Hands-free is switched on on-demand.

[0231] Although the present invention has been described with referenceto preferred embodiments, workers skilled in the art will recognize thatchanges may be made in form and detail without departing from the spiritand scope of the invention.

APPENDIX A

[0232] 1 Introduction

[0233] The following tags are a set of markup elements that allows adocument to use speech as an input or output medium. The tags aredesigned to be self-contained XML that can be imbedded into any SGMLderived markup languages such as HTML, XHTML, cHTML, SMIL, WML and thelike. The tags herein conform generally speech application language tags(SALT). SALT is a developing standard for enabling access toinformation, applications and web services from personal computers,telephones, tablet PCs and wireless mobile devices, for example. TheSALT 1.0 specification may be found online at http://www.SALTforum.org.The tags used herein are similar to SAPI 5.0, which are known methodsavailable from Microsoft Corporation of Redmond, Wash. The tags,elements, events, attributes, properties, return values, etc. are merelyexemplary and should not be considered limiting. Although exemplifiedherein for speech and DTMF recognition, similar tags can be provided forother forms of recognition.

[0234] The main elements herein discussed are: <prompt ...> for speechsynthesis configuration and prompt playing <reco ...> for recognizerconfiguration and recognition execution and post-processing <grammar...> for specifying input grammar resources <bind ...> for processing ofrecognition results <dtmf ...> for configuration and control of DTMF

[0235] 2 Reco

[0236] The Reco element is used to specify possible user inputs and ameans for dealing with the input results. As such, its main elements are<grammar>and <bind>, and it contains resources for configuringrecognizer properties.

[0237] Reco elements are activated programmatically in uplevel browsersvia Start and Stop methods, or in SMIL-enabled browsers by using SMILcommands. They are considered active declaratively in downlevel browsers(i.e. non script-supporting browsers) by their presence on the page. Inorder to permit the activation of multiple grammars in parallel,multiple Reco elements may be considered active simultaneously.

[0238] Recos may also take a partcular mode—‘automatic’, ‘single’ or‘multiple’—to distinguish the kind of recognition scenarios which theyenable and the behaviour of the recognition platform.

[0239] 2.1 Reco Content

[0240] The Reco element contains one or more grammars and optionally aset of bind elements which inspect the results of recognition and copythe relevant portions to values in the containing page.

[0241] In uplevel browsers, Reco supports the programmatic activationand deactivation of individual grammar rules. Note also that alltop-level rules in a grammar are active by default for a recognitioncontext.

[0242] 2.1.1 <Grammar> Element

[0243] The grammar element is used to specify grammars, either inline orreferenced using the src attribute. At least one grammar (either inlineor referenced) is typically specified. Inline grammars can be text-basedgrammar formats, while referenced grammars can be text-based or binarytype. Multiple grammar elements may be specified. If more than onegrammar element is specified, the rules within grammars are added asextra rules within the same grammar. Any rules with the same name willbe overwritten.

[0244] Attributes:

[0245] src: Optional if inline grammar is specified. URI of the grammarto be included. Note that all top-level rules in a grammar are active bydefault for a recognition context.

[0246] langID: Optional. String indicating which language speech engineshould use. The string format follows the xml:lang definition. Forexample, langID=“en-us” denotes US English. This attribute is onlyeffective when the langID is not specified in the grammar URI. Ifunspecified, defaults to US English.

[0247]  If the langID is specified in multiple places then langIDfollows a precedence order from the lowest scope—remote grammar file(i.e language id is specified within the grammar file) followed bygrammar element followed by reco element. <grammar src=“FromCity.xml” />  or <grammar>   <rule toplevel=“active”>     <p>from </p>     <rulerefname=“cities” />   </rule>   <rule name=“cities” >     <l>     <p>Cambridge </p>     <p> Seattle </p>     <p> London </p>     </l>  </rule> </grammar>

[0248] If both a src-referenced grammar and an inline grammar arespecified, the inline rules are added to the referenced rules, and anyrules with the same name will be overwritten.

[0249] 2.1.2 <Bind> Element

[0250] The bind element is used to bind values from the recognitionresults into the page.

[0251] The recognition results consumed by the bind element can be anXML document containing a semantic markup language (SML) for specifyingrecognition results. Its contents include semantic values, actual wordsspoken, and confidence scores. SML could also include alternaterecognition choices (as in an N-best recognition result). A sample SMLdocument for the utterance “I'd like to travel from Seattle to Boston”is illustrated below:   <sml confidence=“40”>     <travel text=“I'd liketo travel from   Seattle to Boston”>       <origin_city confidence=“45”>Seattle </origin_city>       <dest_city confidence=“35”> Boston</dest_city>   </travel> </sml>

[0252] Since an in-grammar recognition is assumed to produce an XMLdocument—in semantic markup language, or SML—the values to be bound fromthe SML document are referenced using an XPath query. And since theelements in the page into which the values will be bound should be areuniquely identified (they are likely to be form controls), these targetelements are referenced directly.

[0253] Attributes:

[0254] targetElement: Required. The element to which the value contentfrom the SML will be assigned (as in W3C SMIL 2.0).

[0255] targetAttribute: Optional. The attribute of the target element towhich the value content from the SML will be assigned (as with theattributeName attribute in SMIL 2.0). If unspecified, defaults to“value”.

[0256] test: Optional. An XML Pattern (as in the W3C XML DOMspecification) string indicating the condition under which therecognition result will be assigned. Default condition is true.

[0257] value: Required. An XPATH (as in the W3C XML DOM specification)string that specifies the value from the recognition result document tobe assigned to the target element.

[0258] Example:

[0259] So given the above SML return, the following reco element usesbind to transfer the values in origin_city and dest_city into the targetpage elements txtBoxOrigin and txtBoxDest: <input name=“txtBoxOrigin”type=“text”/> <input name=“txtBoxDest” type=“text” /> <reco id=“travel”>  <grammar src=“./city.xml” />   <bind targetElement=“txtBoxOrigin”    value=“//origin_city” />   <bind targetElement=“txtBoxDest”    value=“//dest_city” /> </reco>

[0260] This binding may be conditional, as in the following example,where a test is made on the confidence attribute of the dest_city resultas a pre-condition to the bind operation: <bindtargetElement=“txtBoxDest”   value=“//dest_city”  test=“/sml/dest_city[@confidence $gt$ 40]” />

[0261] The bind element is a simple declarative means of processingrecognition results on downlevel or uplevel browsers. For more complexprocessing, the reco DOM object supported by uplevel browsers implementsthe onReco event handler to permit programmatic script analysis andpost-processing of the recognition return.

[0262] 2.2 Attributes and Properties

[0263] The following attributes are supported by all browsers, and theproperties by uplevel browsers.

[0264] 2.2.1 Attributes

[0265] The following attributes of Reco are used to configure the speechrecognizer for a dialog turn.

[0266] initialTimeout: Optional. The time in milliseconds between startof recognition and the detection of speech. This value is passed to therecognition platform, and if exceeded, an onSilence event will beprovided from the recognition platform (see 2.4.2). If not specified,the speech platform will use a default value.

[0267] babbleTimeout: Optional. The period of time in milliseconds inwhich the recognizer must return a result after detection of speech. Forrecos in automatic and single mode, this applies to the period betweenspeech detection and the stop call. For recos in ‘multiple’ mode, thistimeout applies to the period between speech detection and eachrecognition return—i.e. the period is restarted after each return ofresults or other event. If exceeded, different events are thrownaccording to whether an error has occurred or not. If the recognizer isstill processing audio—eg in the case of an exceptionally longutterance—the onNoReco event is thrown, with status code 13 (see 2.4.4).If the timeout is exceeded for any other reason, however, a recognizererror is more likely, and the onTimeout event is thrown. If notspecified, the speech platform will default to an internal value.

[0268] maxTimeout: Optional. The period of time in milliseconds betweenrecognition start and results returned to the browser. If exceeded, theonTimeout event is thrown by the browser—this caters for network orrecognizer failure in distributed environments. For recos in ‘multiple’mode, as with babbleTimeout, the period is restarted after the return ofeach recognition or other event. Note that the maxTimeout attributeshould be greater than or equal to the sum of initialTimeout andbabbleTimeout. If not specified, the value will be a browser default.

[0269] endSilence: Optional. For Recos in automatic mode, the period ofsilence in milliseconds after the end of an utterance which must be freeof speech after which the recognition results are returned. Ignored forrecos of modes other than automatic. If unspecified, defaults toplatform internal value.

[0270] reject: Optional. The recognition rejection threshold, belowwhich the platform will throw the ‘no reco’ event. If not specified, thespeech platform will use a default value. Confidence scores rangebetween 0 and 100 (integer). Reject values lie in between.

[0271] server: Optional. URI of speech platform (for use when the taginterpreter and recognition platform are not co-located). An examplevalue might be server=protocol://yourspeechplatform. An applicationwriter is also able to provide speech platform specific settings byadding a querystring to the URI string, egprotocol://yourspeechplatform?bargeinEnergyThreshold=0.5.

[0272] langID: Optional. String indicating which language speech engineshould use. The string format follows the xml:lang definition. Forexample, langID=“en-us” denotes US English. This attribute is onlyeffective when the langID is not specified in the grammar element (see2.1.1).

[0273] mode: Optional. String specifying the recognition mode to befollowed. If unspecified, defaults to “automatic” mode.

[0274] 2.2.2 Properties

[0275] The following properties contain the results returned by therecognition process (these are supported by uplevel browsers).

[0276] recoResult Read-only. The results of recognition, held in an XMLDOM node object containing semantic markup language (SML), as describedin 2.1.2, In case of no recognition, the property returns null.

[0277] text Read-only. A string holding the text of the words recognized(i.e., a shorthand for contents of the text attribute of the highestlevel element in the SML recognition return in recoResult.

[0278] status: Read-only. Status code returned by the recognitionplatform. Possible values are 0 for successful recognition, or thefailure values −1 to −4 (as defined in the exceptions possible on theStart method (section 2.3.1) and Activate method (section 2.3.4)), andstatuses −11 to −15 set on the reception of recognizer events (see 2.4).

[0279] 2.3 Object Methods

[0280] Reco activation and grammar activation may be controlled usingthe following methods in the Reco's DOM object. With these methods,uplevel browsers can start and stop Reco objects, cancel recognitions inprogress, and activate and deactivate individual grammar top-level rules(uplevel browsers only).

[0281] 2.3.1 Start

[0282] The Start method starts the recognition process, using as activegrammars all the top-level rules for the recognition context which havenot been explicitly deactivated.

[0283] Syntax:

[0284] Object.Start( )

[0285] Return value:

[0286] None.

[0287] Exception:

[0288] The method sets a non-zero status code and fires an onNoRecoevent when fails. Possible failures include no grammar (reco status=−1),failure to load a grammar, which could be a variety of reasons likefailure to compile grammar, non-existent URI (reco status=−2), or speechplatform errors (reco status=−3).

[0289] 2.3.2 Stop

[0290] The Stop method is a call to end the recognition process. TheReco object stops recording audio, and the recognizer returnsrecognition results on the audio received up to the point whererecording was stopped. All the recognition resources used by Reco arereleased, and its grammars deactivated. (Note that this method need notbe used explicitly for typical recognitions in automatic mode, since therecognizer itself will stop the reco object on endpoint detection afterrecognizing a complete sentence.) If the Reco has not been started, thecall has no effect.

[0291] Syntax:

[0292] Object.Stop( )

[0293] Return value:

[0294] None.

[0295] Exception:

[0296] None.

[0297] 2.3.3 Cancel

[0298] The Cancel method stops the audio feed to the recognizer,deactivates the grammar and releases the recognizer and discards anyrecognition results. The browser will disregard a recognition result forcanceled recognition. If the recognizer has not been started, the callhas no effect.

[0299] Syntax:

[0300] Object.Cancel( )

[0301] Return value:

[0302] None.

[0303] Exception:

[0304] None.

[0305] 2.3.4 Activate

[0306] The Activate method activates a top-level rule in the contextfree grammar (CFG). Activation must be called before recognition begins,since it will have no effect during a ‘Started’ recognition process.Note that all the grammar top-level rules for the recognition contextwhich have not been explicitly deactivated are already treated asactive.

[0307] Syntax:

[0308] Object.Activate(strName);

[0309] Parameters:

[0310] strName: Required. Rule name to be activated.

[0311] Return value:

[0312] None.

[0313] Exception:

[0314] None.

[0315] 2.3.5 Deactivate

[0316] The method deactivates a top-level rule in the grammar. If therule does not exist, the method has no effect.

[0317] Syntax:

[0318] Object.Deactivate(strName);

[0319] Parameters:

[0320] strName: Required. Rule name to be deactivated. An empty stringdeactivates all rules.

[0321] Return value

[0322] None.

[0323] Exception

[0324] None.

[0325] 2.4 Reco Events

[0326] The Reco DOM object supports the following events, whose handlersmay be specified as attributes of the reco element.

[0327] 2.4.1 onReco:

[0328] This event gets fired when the recognizer has a recognitionresult available for the browser. For recos in automatic mode, thisevent stops the recognition process automatically and clears resources(see 2.3.2). OnReco is typically used for programmatic analysis of therecognition result and processing of the result into the page.

[0329] Syntax: Inline HTML <Reco onReco = “handler” > Event propertyObject.onReco = handler; Object.onReco = GetRef(“handler”);

[0330] Event Object Info: Bubbles No To invoke User says somethingDefault Return recognition result object action

[0331] Event Properties:

[0332] Although the event handler does not receive properties directly,the handler can query the event object for data (see the use of theevent object in the example below).

[0333] Example

[0334] The following XHTML fragment uses onReco to call a script toparse the recognition outcome and assign the values to the properfields. <input name=“txtBoxOrigin” type=“text” /> <inputname=“txtBoxDest” type=“text” /> <recoonReco=“processCityRecognition()”/>   <grammarsrc=“/grammars/cities.xml” /> </reco> <script><![CDATA[   functionprocessCityRecognition () {     smlResult = event.srcElement.recoResult;    origNode = smlResult.selectSingleNode(“//origin_city”);     if(origNode != null) txtBoxOrigin.value = origNode.text;     destNode =smlResult.selectSingleNode(“//dest_city”);     if (destNode != null)txtBoxDest.value = destNode.text;     }   ]]></script>

[0335] 2.4.2 onSilence:

[0336] onSilence handles the event of no speech detected by therecognition platform before the duration of time specified in theinitialTimeout attribute on the Reco (see 2.2.1). This event cancels therecognition process automatically for the automatic recognition mode.

[0337] Syntax: Inline HTML <reco onSilence=“handler” . . . > Eventproperty (in Object.onSilence = handler ECMAScript) Object.onSilence =GetRef(“handler”);

[0338] Event Object Info: Bubbles No To invoke Recognizer did not detectspeech within the period specified in the initialTimeout attribute.Default Set status = −11 action

[0339] Event Properties:

[0340] Although the event handler does not receive properties directly,the handler can query the event object for data.

[0341] 2.4.3 onTimeout

[0342] onTimeout handles two types of event which typically reflecterrors from the speech platform.

[0343] It handles the event thrown by the tags interpreter which signalsthat the period specified in the maxtime attribute (see 2.2.1) expiredbefore recognition was completed. This event will typically reflectproblems that could occur in a distributed architecture.

[0344] It also handles (ii) the event thrown by the speech recognitionplatform when recognition has begun but processing has stopped without arecognition within the period specified by babbleTimeout (see 2.2.1).

[0345] This event cancels the recognition process automatically.

[0346] Syntax: Inline HTML <reco onTimeout=“handler” . . . > Eventproperty (in Object.onTimeOut = handler ECMAScript) Object.onTimeOut =GetRef(“handler”);

[0347] Event Object Info: Bubbles No To invoke Thrown by the browserwhen the period set by the maxtime attribute expires before recognitionis stopped. Default Set reco status to −12. action

[0348] Event Properties:

[0349] Although the event handler does not receive properties directly,the handler can query the event object for data.

[0350] 2.4.4 onNoReco:

[0351] onNoReco is a handler for the event thrown by the speechrecognition platform when it is unable to return valid recognitionresults. The different cases in which this may happen are distinguishedby status code. The event stops the recognition process automatically.

[0352] Syntax: Inline HTML <Reco onNoReco =“handler” > Event propertyObject.onNoReco = handler; Object.onNoReco = GetRef(“handler”);

[0353] Event Object Info: Bubbles No To invoke Recognizer detects soundbut is unable to interpret the utterance. Default Set status propertyand return null action recognition result. Status codes are set asfollows: status -13: sound was detected but no speech was able to beinterpreted; status -14: some speech was detected and interpreted butrejected with insufficient confidence (for threshold setting, see thereject attribute in 2.2.1). status -15: speech was detected andinterpreted, but a complete recognition was unable to be returnedbetween the detection of speech and the duration specified in thebabbleTimeout attribute (see 2.2.1).

[0354] Event Properties:

[0355] Although the event handler does not receive properties directly,the handler can query the event object for data.

[0356] 3 Prompt

[0357] The prompt element is used to specify system output. Its contentmay be one or more of the following:

[0358] inline or referenced text, which may be marked up with prosodicor other speech output information;

[0359] variable values retrieved at render time from the containingdocument;

[0360] links to audio files.

[0361] Prompt elements may be interpreted declaratively by downlevelbrowsers (or activated by SMIL commands), or by object methods onuplevel browsers.

[0362] 3.1 Prompt Content

[0363] The prompt element contains the resources for system output,either as text or references to audio files, or both.

[0364] Simple prompts need specify only the text required for output,eg: <prompt id=“Welcome”>   Thank you for calling ACME weather report.</prompt>

[0365] This simple text may also contain further markup of any of thekinds described below.

[0366] 3.1.1 Speech Synthesis Markup

[0367] Any format of speech synthesis markup language can be used insidethe prompt element. (This format may be specified in the ‘tts’ attributedescribed in 3.2.1.) The following example shows text with aninstruction to emphasize certain words within it:   <promptid=“giveBalance”>     You have <emph> five dollars </emph> left in youraccount.   </prompt>

[0368] 3.1.2 Dynamic Content

[0369] The actual content of the prompt may need to be computed on theclient just before the prompt is output. In order to confirm aparticular value, for example, the value needs to be dereferenced in avariable. The value element may be used for this purpose.

[0370] Value Element

[0371] value: Optional. Retrieves the values of an element in thedocument.

[0372] Attributes:

[0373] targetElement: Optional. Either href or targetElement must bespecified. The id of the element containing the value to be retrieved.

[0374] targetAttribute: Optional. The attribute of the element fromwhich the value will be retrieved.

[0375] href: Optional. The URI of an audio segment. href will overridetargetElement if both are present.

[0376] The targetElement attribute is used to reference an elementwithin the containing document. The content of the element whose id isspecified by targetElement is inserted into the text to be synthesized.If the desired content is held in an attribute of the element, thetargetAttribute attribute may be used to specify the necessary attributeon the targetElement. This is useful for dereferencing the values inHTML form controls, for example. In the following illustration, the“value” attributes of the “txtBoxOrigin” and “txtBoxDest” elements areinserted into the text before the prompt is output   <promptid=“Confirm”>     Do you want to travel from     <valuetargetElement=“txtBoxOrigin” targetAttribute=“value” />     to    <value targetElement=“txtBoxDest” targetAttribute=“value” />     ?  </prompt>

[0377] 3.1.3 Audio Files

[0378] The value element may also be used to refer to a pre-recordedaudio file for playing instead of, or within, a synthesized prompt. Thefollowing example plays a beep at the end of the prompt: <prompt>  After the beep, please record your message.   <valuehref=“/wav/beep.wav” /> </prompt>

[0379] 3.1.4 Referenced Prompts

[0380] Instead of specifying content inline, the src attribute may beused with an empty element to reference external content via URI, as in:  <prompt id=“Welcome” src=“/ACMEWeatherPrompts#Welcome” />

[0381] The target of the src attribute can hold any or all of the abovecontent specified for inline prompts.

[0382] 3.2 Attributes and Properties

[0383] The prompt element holds the following attributes (downlevelbrowsers) and properties (downlevel and uplevel browsers).

[0384] 3.2.1 Attributes

[0385] tts: Optional. The markup language type for text-to-speechsynthesis. Default is “SAPI 5”.

[0386] src: Optional if an inline prompt is specified. The URI of areferenced prompt (see 3.1.4).

[0387] bargein: Optional. Integer. The period of time in millisecondsfrom start of prompt to when playback can be interrupted by the humanlistener. Default is infinite, i.e., no bargein is allowed. Bargein=0allows immediate bargein. This applies to whichever kind of barge-in issupported by platform. Either keyword or energy-based bargein times canbe configured in this way, depending on which is enabled at the time thereco is started.

[0388] prefetch: Optional. A Boolean flag indicating whether the promptshould be immediately synthesized and cached at browser when the page isloaded. Default is false.

[0389] 3.2.2 Properties

[0390] Uplevel browsers support the following properties in the prompt'sDOM object.

[0391] bookmark: Read-only. A string object recording the text of thelast synthesis bookmark encountered.

[0392] status: Read-only. Status code returned by the speech platform.

[0393] 3.3 Prompt Methods

[0394] Prompt playing may be controlled using the following methods inthe prompt's DOM object. In this way, uplevel browsers can start andstop prompt objects, pause and resume prompts in progress, and changethe speed and volume of the synthesized speech.

[0395] 3.3.1 Start

[0396] Start playback of the prompt. Unless an argument is given, themethod plays the contents of the object. Only a single prompt object isconsidered ‘started’ at a given time, so if Start is called insuccession, all playbacks are played in sequence.

[0397] Syntax:

[0398] Object.Start([strText]);

[0399] Parameters:

[0400] strText: the text to be sent to the synthesizer. If present, thisargument overrides the contents of the object.

[0401] Return value:

[0402] None.

[0403] Exception:

[0404] Set status=−1 and fires an onComplete event if the audio bufferis already released by the server.

[0405] 3.3.2 Pause

[0406] Pause playback without flushing the audio buffer. This method hasno effect if playback is paused or stopped.

[0407] Syntax:

[0408] Object.Pause( );

[0409] Return value:

[0410] None.

[0411] Exception:

[0412] None.

[0413] 3.3.3 Resume

[0414] Resume playback without flushing the audio buffer. This methodhas no effect if playback has not been paused.

[0415] Syntax:

[0416] Object.Resume( );

[0417] Return value:

[0418] None.

[0419] Exception:

[0420] Throws an exception when resume fails.

[0421] 3.3.4 Stop

[0422] Stop playback, if not already, and flush the audio buffer. If theplayback has already been stopped, the method simply flushes the audiobuffer.

[0423] Syntax:

[0424] Object.Stop( );

[0425] Return value:

[0426] None.

[0427] Exception:

[0428] None.

[0429] 3.3.5 Change

[0430] Change speed and/or volume of playback. Change may be calledduring playback.

[0431] Syntax:

[0432] Object.Change(speed, volume);

[0433] Parameters:

[0434] speed: Required. The factor to change. Speed=2.0 means double thecurrent rate, speed=0.5 means halve the current rate, speed=0 means torestore the default value.

[0435] volume: Required. The factor to change. Volume=2.0 means doublethe current volume, volume=0.5 means halve the current volume, volume=0means to restore the default value.

[0436] Return value:

[0437] None.

[0438] Exception:

[0439] None.

[0440] 3.3.6 Prompt Control Example

[0441] The following example shows how control of the prompt using themethods above might be authored for a platform which does not support akeyword barge-in mechanism. <html> <title>Prompt control</title> <head> <script>   <!--     function checkKWBargein( ) {      news.change(1.0,0.5); // turn down the   volume while verifying      if (keyword.text ==“”) { // result is below   threshold      news.change(1.0, 2.0); //restore the   volume      keyword.Start( ); // restart the   recognition    } else {      news.Stop( ); // keyword detected! Stop   the prompt     // Do whatever that is necessary     }    } //  </script> <scriptfor=“window” event=“onload”>   <!--    news.Start( ); keyword.Start( );  //  </script>   </head> <body>  <prompt id=“news” bargein=“0”>

[0442] Stocks turned in another lackluster performance Wednesday asinvestors received little incentive to make any big moves ahead of nextweek's Federal Reserve meeting. The tech-heavy Nasdaq Composite Indexdropped 42.51 points to close at 2156.26. The Dow Jones IndustrialAverage fell 17.05 points to 10866.46 after an early-afternoon rallyfailed. - <!--  </prompt>   <reco  id=“keyword”     reject=“70”    onReco=“checkKWBargein( )” >     <grammar  src=http://denali/newsbargein grammar.xml />   </reco> </body> </html>

[0443] 3.4 Prompt Events

[0444] The prompt DOM object supports the following events, whosehandlers may be specified as attributes of the prompt element.

[0445] 3.4.1 onBookmark

[0446] Fires when a synthesis bookmark is encountered.

[0447] The event does not pause the playback.

[0448] Syntax: Inline HTML <prompt onBookmark=“handler” . . . > Eventproperty Object.onBookmark = handler Object.onBookmark =GetRef(“handler”);

[0449] Event Object Info: Bubbles No To invoke A bookmark in therendered string is encountered Default Returns the bookmark stringaction

[0450] Event Properties:

[0451] Although the event handler does not receive properties directly,the handler can query the event object for data.

[0452] 3.4.2 onBargein:

[0453] Fires when a user's barge-in event is detected. (Note thatdetermining what constitutes a barge-in event, eg energy detection orkeyword recognition, is up to the platform.) A specification of thisevent handler does not automatically turn the barge-in on.

[0454] Syntax: Inline HTML <prompt onBargein=”handler” ...> Eventproperty Object.onBargein = handler Object.onBargein =GetRef(“handler”);

[0455] Event Object Info: Bubbles No To invoke A bargein event isencountered Default None action

[0456] Event Properties:

[0457] Although the event handler does not receive properties directly,the handler can query the event object for data.

[0458] 3.4.3 onComplete:

[0459] Fires when the prompt playback reaches the end or exceptions (asdefined above) are encountered.

[0460] Syntax: Inline HTML <prompt onComplete=”handler” ...> Eventproperty Object. onComplete = handler Object. onComplete =GetRef(“handler”);

[0461] Event Object Info: Bubbles No To invoke A prompt playbackcompletes Default Set status = 0 if playback completes action normally,otherwise set status as specified above.

[0462] Event Properties:

[0463] Although the event handler does not receive properties directly,the handler can query the event object for data.

[0464] 3.4.4 Using Bookmarks and Events

[0465] The following example shows how bookmark events can be used todetermine the semantics of a user response—either a correction to adeparture city or the provision of a destination city—in terms of whenbargein happened during the prompt output. The onBargein handler calls ascript which sets a global ‘mark’ variable to the last bookmarkencountered in the prompt, and the value of this ‘mark’ is used in thereco's postprocessing function (‘heard’) to set the correct value.  <script><![CDATA[     var mark;     function interrupt( ) {       mark= event.srcElement.bookmark;     }     function ProcessCityConfirm( ) {      confirm.stop( ); // flush the audio buffer       if (mark ==“mark_origin_city”)         txtBoxOrigin.value = event.srcElement.text;      else         txtBoxDest.value = event.srcElement.text;     }  ]]></script>   <body>   <input name=“txtBoxOrigin” value=“Seattle”type=“text”/>   <input name=“txtBoxDest” type=“text” />   ...   <promptid=“confirm” onBargein=“interrupt( )” bargein=“0”>     From <bookmarkmark=“mark_origin_city” />     <value targetElement=“orgin”targetAttribute=“value” />,     please say <bookmarkmark=“mark_dest_city” /> the     destination city you want to travel to.  </prompt>   <reco onReco=“ProcessCityConfirm( )” >     <grammarsrc=“/grm/1033/cities.xml” />   </reco>   ...   </body>

[0466] 4 DTMF

[0467] Creates a DTMF recognition object. The object can be instantiatedusing inline markup language syntax or in scripting. When activated,DTMF can cause prompt object to fire a barge-in event. It should benoted the tags and eventing discussed below with respect to DTMFrecognition and call control discussed in Section 5 generally pertain tointeraction between the voice browser 216 and media server 214.

[0468] 4.1 Content

[0469] dtmfgrammar: for inline grammar.

[0470] bind: assign DTMF conversion result to proper field.

[0471] Attributes:

[0472] targetElement: Required. The element to which a partialrecognition result will be assigned to (cf. same as in W3C SMIL 2.0).

[0473] targetAttribute: the attribute of the target element to which therecognition result will be assigned to (cf. same as in SMIL 2.0).Default is “value”.

[0474] test: condition for the assignment. Default is true.

EXAMPLE 1 Map Keys to Text

[0475]   <input type=“text” name=“city” />   <DTMF id=“city_choice”timeout=“2000” numDigits=“1”>     <dtmfgrammar>       <keyvalue=“1”>Seattle</key>       <key value=“2”>Boston</key>    </dtmfgrammar>     <bind targetElement=“city”targetAttribute=“value” />   </DTMF>

[0476] When “city_choice” is activated, “Seattle” will be assigned tothe input field if the user presses 1, “Boston” if 2, nothing otherwise.

EXAMPLE 2 How DTMF can be Used with Multiple Fields

[0477]   <input type=“text” name=“area_code” />   <input type=“text”name=“phone_number” />   <DTMF id=“areacode” numDigits=“3”onReco=“extension.Activate( )”>     <bind targetElement=“area_code” />  </DTMF>   <DTMF id=“extension” numDigits=“7”>     <bindtargetElement=“phone_number” />   </DTMF>

[0478] This example demonstrates how to allow users entering intomultiple fields.

EXAMPLE 3 How to Allow Both Speech and DTMF Inputs and Disable Speechwhen User Starts DTMF

[0479] <input type=“text” name=“credit_card_number” /> <promptonBookmark=“dtmf.Start( ); speech.Start( )”    bargein=“0”>   Please say<bookmark name=“starting” />   or enter your credit card number now  </prompt>   <DTMF id=“dtmf” escape=“#” length=“16”interdigitTimeout=“2000”     onkeypress=“speech.Stop( )”>     <bindtargetElement=“credit_card_number” />   </DTMF>   <reco id=“speech” >    <grammar src=“/grm/1033/digits.xml” />     <bindtargetElement=“credit_card_number” />   </reco>

[0480] 4.2 Attributes and Properties

[0481] 4.2.1 Attributes

[0482] dtmfgrammar: Required. The URI of a DTMF grammar.

[0483] 4.2.2 Properties

[0484] DTMFgrammar Read-Write.

[0485] An XML DOM Node object representing DTMF to string conversionmatrix (also called DTMF grammar). The default grammar is <dtmfgrammar>  <key value=“0”>0</key>   <key value=“1”>1</key>   ...   <keyvalue=“9”>9</key>   <key value=“*”>*</key>   <key value=“#”>#</key></dtmfgrammar >

[0486] flush

[0487] Read-write, a Boolean flag indicating whether to automaticallyflush the DTMF buffer on the underlying telephony interface card beforeactivation. Default is false to enable type-ahead.

[0488] escape

[0489] Read-Write. The escape key to end the DTMF reading session.Escape key is one key.

[0490] numDigits

[0491] Read-Write. Number of key strokes to end the DTMF readingsession. If both escape and length are specified, the DTMF session isended when either condition is met.

[0492] dtmfResult

[0493] Read-only string, storing the DTMF keys user has entered. Escapeis included in result if typed.

[0494] text

[0495] Read-only string storing white space separated token string,where each token is converted according to DTMF grammar.

[0496] initialTimeout

[0497] Read-Write. Timeout period for receiving the first DTMF keystoke,in milliseconds. If unspecified, defaults to the telephony platform'sinternal setting.

[0498] interdigitTimeout

[0499] Read-Write. Timeout period for adjacent DTMF keystokes, inmilliseconds. If unspecified, defaults to the telephony platform'sinternal setting.

[0500] 4.3 Object Methods:

[0501] 4.3.1 Start

[0502] Enable DTMF interruption and start a DTMF reading session.

[0503] Syntax:

[0504] Object.Start( );

[0505] Return value:

[0506] None

[0507] Exception:

[0508] None

[0509] 4.3.2 Stop

[0510] Disable DTMF. The key strokes entered by the user, however,remain in the buffer.

[0511] Syntax:

[0512] Object.Stop( );

[0513] Return value:

[0514] None

[0515] Exception:

[0516] None

[0517] 4.3.3 Flush

[0518] Flush the DTMF buffer. Flush can not be called during a DTMFsession.

[0519] Syntax:

[0520] Object.Flush( );

[0521] Return value:

[0522] None

[0523] Exception:

[0524] None

[0525] 4.4 Events

[0526] 4.4.1 onkeypress

[0527] Fires when a DTMF key is press. This overrides the default eventinherited from the HTML control. When user hits the escape key, theonRec event fires, not onKeypress.

[0528] Syntax: Inline HTML <DTMF onkeypress=”handler” ...> Eventproperty Object.onkeypress = handler Object.onkeypress =GetRef(“handler”);

[0529] Event Object Info: Bubbles No To invoke Press on the touch-tonetelephone key pad Default Returns the key being pressed action

[0530] Event Properties:

[0531] Although the event handler does not receive properties directly,the handler can query the event object for data.

[0532] 4.4.2 onReco

[0533] Fires when a DTMF session is ended. The event disables thecurrent DTMF object automatically.

[0534] Syntax: Inline HTML <DTMF onReco=”handler” ...> Event propertyObject.onReco = handler Object.onReco = GetRef(“handler”);

[0535] Event Object Info: Bubbles No To invoke User presses the escapekey or the number of key strokes meets specified value. Default Returnsthe key being pressed action

[0536] Event Properties:

[0537] Although the event handler does not receive properties directly,the handler can query the event object for data.

[0538] 4.4.3 onTimeout

[0539] Fires when no phrase finish event is received before time out.The event halts the recognition process automatically.

[0540] Syntax: Inline HTML <DTMF onTimeout=”handler” ...> Event property(in Object.onTimeout = handler ECMAScript) Object.onTimeout =GetRef(“handler”);

[0541] Event Object Info: Bubbles No To invoke No DTMF key stroke isdetected within the timeout specified. Default None action

[0542] Event Properties:

[0543] Although the event handler does not receive properties directly,the handler can query the event object for data.

[0544] 5 CallControl Object

[0545] Represents the telephone interface (call, terminal, andconnection) of the telephone voice browser. This object is as native aswindow object in a GUI browser. As such, the lifetime of the telephoneobject is the same as the browser instance itself. A voice browser fortelephony instantiates the telephone object, one for each call. Usersdon't instantiate or dispose the object.

[0546] At this point, only features related to first-party call controlsare exposed through this object.

[0547] 5. 1 Properties

[0548] address

[0549] Read-only. XML DOM node object. Implementation specific. This isthe address of the caller. For PSTN, may a combination of ANI and ALI.For VoIP, this is the caller's IP address.

[0550] ringsBeforeAnswer

[0551] Number of rings before answering an incoming call. Default isinfinite, meaning the developer must specifically use the Answer( )method below to answer the phone call. When the call center uses ACD toqueue up the incoming phone calls, this number can be set to 0.

[0552] 5.2 Methods

[0553] Note: all the methods here are synchronous.

[0554] 5.2.1 Transfer

[0555] Transfers the call. For a blind transfer, the system mayterminate the original call and free system resources once the transfercompletes.

[0556] Syntax:

[0557] telephone.Transfer(strText);

[0558] Parameters:

[0559] strText: Required. The address of the intended receiver.

[0560] Return value:

[0561] None.

[0562] Exception:

[0563] Throws an exception when the call transfer fails. e.g., when endparty is busy, no such number, fax or answering machine answers.

[0564] 5.2.2 Bridge

[0565] Third party transfer. After the call is transferred, the browsermay release resources allocated for the call. It is up to theapplication to recover the session state when the transferred callreturns using strUID. The underlying telephony platform may route thereturning call to a different browser. The call can return only when therecipient terminates the call.

[0566] Syntax:

[0567] telephone.Bridge(strText, strUID, [imaxTime]);

[0568] Parameters:

[0569] strText: Required. The address of the intended receiver.

[0570] strUID: Required. The session ID uniquely identifying the currentcall. When the transferred call is routed back, the srtUID will appearin the address attribute.

[0571] imaxTime: Optional. Maximum duration in seconds of thetransferred call. If unspecified, defaults to platform-internal value

[0572] Return value:

[0573] None.

[0574] Exception:

[0575] None.

[0576] 5.2.3 Answer

[0577] Answers the phone call.

[0578] Syntax:

[0579] telephone.Answer( );

[0580] Return value:

[0581] None.

[0582] Exception:

[0583] Throws an exception when there is no connection. No onAnswerevent will be fired in this case.

[0584] 5.2.4 Hangup

[0585] Terminates the phone call. Has no effect if no call currently inprogress.

[0586] Syntax:

[0587] telephone.Hangup( );

[0588] Return value:

[0589] None.

[0590] Exception:

[0591] None.

[0592] 5.2.5 Connect

[0593] Starts a first-party outbound phone call.

[0594] Syntax:

[0595] telephone.Connect(strText, [iTimeout]);

[0596] Parameters:

[0597] strText: Required. The address of the intended receiver.

[0598] iTimeout: Optional. The time in milliseconds before abandoningthe attempt. If unspecified, defaults to platform-internal value.

[0599] Return value:

[0600] None.

[0601] Exception:

[0602] Throws an exception when the call cannot be completed, includingencountering busy signals or reaching a FAX or answering machine (Note:hardware may not support this feature).

[0603] 5.2.6 Record

[0604] Record user audio to file.

[0605] Syntax:

[0606] telephone.Record(url, endSilence, [maxTimeout],[initialTimeout]);

[0607] Parameters:

[0608] url: Required. The url of the recorded results.

[0609] endSilence: Required. Time in milliseconds to stop recordingafter silence is detected.

[0610] maxTimeout: Optional. The maximum time in seconds for therecording. Default is platform-specific.

[0611] initialTimeout: Optional. Maximum time (in milliseconds) ofsilence allowed at the beginning of a recording.

[0612] Return value:

[0613] None.

[0614] Exception:

[0615] Throws an exception when the recording can not be written to theurl.

[0616] 5.3 Event Handlers

[0617] App developers using telephone voice browser may implement thefollowing event handlers.

[0618] 5.3.1 onIncoming( )

[0619] Called when the voice browser receives an incoming phone call.All developers can use this handler to read caller's address and invokecustomized features before answering the phone call.

[0620] 5.3.2 onAnswer( )

[0621] Called when the voice browser answers an incoming phone call.

[0622] 5.3.3 onHangup( )

[0623] Called when user hangs up the phone. This event is NOTautomatically fired when the program calls the Hangup or Transfermethods.

[0624] 5.4 Example

[0625] This example shows scripting wired to the call control events tomanipulate the telephony session. <HTML> <HEAD>  <TITLE>LogonPage</TITLE>  </HEAD>   <SCRIPT>   var focus;   function RunSpeech( ) {    if (logon.user.value == “”) {       focus=“user”;       p_uid.Start(); g_login.Start( );   dtmf.Start( ); return;     }     if(logon.pass.value == “”) {       focus=“pin”;       p_pin.Start( );g_login.Start( );   dtmf.Start( ); return;     }     p_thank.Start( );logon.submit( );   }   function login_reco( ) {     res =event.srcElement.recoResult;     pNode = res.selectSingleNode(“//uid”);    if (pNode != null)       logon.user.value = pNode.xml;     pNode =res.selectSingleNode(“//password”);     if (pNode != null)      logon.pass.value = pNode.xml;   }   function dtmf_reco( ) {    res = event.srcElement.dtmfResult;     if (focus == “user”)      logon.user.value = res;     else       logon.pin.value = res;   }  </SCRIPT>  <SCRIPT for=“callControl” event=“onIncoming”>   <!--     //read address, prepare customized stuff if   any     callControl.Answer();   //   </SCRIPT> <SCRIPT for=“callControl” event=“onOffhook”>   <!--    p_main.Start( ); g_login.Start( ); dtmf.Start( );   focus=“user”;  //   </SCRIPT> <SCRIPT for=“window” event=“onload”>   <!--     if(logon.user.value != “”) {       p_retry.Start( );      logon.user.value = “”;       logon.pass.value = “”;      checkFields( );     } /   </SCRIPT> <BODY>  <reco id=“g_login”    onReco=“login_reco( ); runSpeech( )”     timeout=“5000”    onTimeout=“p_miss.Start( ); RunSpeech( )” >     <grammar  src=http://kokanee1/etradedemo/speechonly/login.xml/>     </ reco > <dtmf id=“dtmf”     escape=“#”     onkeypress=“g_login.Stop( );”    onReco=“dtmf_reco( );RunSpeech( )”     interdigitTimeout=“5000”    onTimeout=“dtmf.Flush( );     p_miss.Start( );RunSpeech( )” /> <prompt id=“p_main”>Please say your user I D and pin  number</prompt> <prompt id=“p_uid”>Please just say your user I  D</prompt>  <promptid=“p_pin”>Please just say your pin  number</prompt>  <promptid=“p_miss”>Sorry, I missed that</prompt>  <prompt id=“p_thank”>Thankyou. Please wait while I  verify your identity</prompt>  <promptid=“p_retry”>Sorry, your user I D and pin  number do not match</prompt> <H2>Login</H2> <form id=“logon”>     UID: <input name=“user”type=“text”     onChange=“runSpeech( )” />     PIN: <input name=“pass”type=“password”     onChange=“RunSpeech( )” />  </form>  </BODY> </HTML>

[0626] 6 Controlling Dialog Flow

[0627] 6.1 Using HTML and Script to Implement Dialog Flow

[0628] This example shows how to implement a simple dialog flow whichseeks values for input boxes and offers context-sensitive help for theinput. It uses the title attribute on the HTML input mechanisms (used ina visual browser as a “tooltip” mechanism) to help form the content ofthe help prompt. <html>  <title>Context Sensitive Help</title> <head> <script> var focus;     function RunSpeech( ) {       if(trade.stock.value == “”) {         focus=“trade.stock”;        p_stock.Start( );         return;       }       if(trade.op.value == “”) {         focus=“trade.op”;         p_op.Start();         return;       }       //.. repeat above for all fields      trade.submit( );     }     function handle( ) {       res =event.srcElement.recoResult;       if (res.text == “help”) {        text = “Please just say”;         text +=document.all[focus].title;         p_help.Start(text);       } else {        // proceed with value assignments         }       }   </script>  </head> <body>   <prompt id=“p_help” onComplete=“checkFileds( )” />  <prompt id=“p_stock”   onComplete=“g_stock.Start( )”>Please say thestock   name</prompt>   <prompt id=“p_op” onComplete=“g_op.Start( )”>Doyou   want to buy or sell</prompt>   <prompt id=“p_quantity”  onComplete=“g_quantity.Start( )”>How many   shares?</prompt>   <promptid=“p_price”   onComplete=“g_price.Start( )”>What's the price</prompt>  <reco id=“g_stock” onReco=“handle( ); checkFields( )” >     <grammarsrc=“./g_stock.xml” />   </ reco >   <reco id=“g_op” onReco=“handle( );checkFields( )” />     <grammar src=“./g_op.xml” />   </ reco >   <recoid=“g_quantity” onReco=“handle( ); checkFields( )”   />     <grammarsrc=“./g_quant.xml” />   </ reco >   <reco id=“g_price” onReco=“handle(); checkFields( )” />     <grammar src=“./g_quant.xml” />   </ reco >  <form id=“trade”>     <input name=“stock” title=“stock name” />    <select name=“op” title=“buy or sell”>       <option value=“buy” />      <option value=“sell” />       </select>     <input name=“quantity”title=“number of shares”   />     <input name=“price” title=“price” />  </form>   </body>   </html>

[0629] 6.2 Using SMIL

[0630] The following example shows activation of prompt and recoelements using SMIL mechanisms. <htmlxmlns:t=“urn:schemas-microsoft-com:time”xmlns:sp=“urn:schemas-microsoft- com:speech”> <head> <style> .time {behavior: url (#default#time2); } </style> </head> <body> <inputname=“txtBoxOrigin” type=“text”/> <input name=“txtBoxDest” type=“text”/> <sp: prompt span>“time” t:begin=“0” > Please say the origin anddestination cities </sp:prompt> <t:par t:begin=“time.end”t:repeatCount=“indefinitely” <sp:reco class=“time” > <grammarsrc=“./city.xml” /> <bind targetElement=“txtBoxOrigin”value=“//origin_city” /> <bind targetElement=“txtBoxDest”test=“/sml/dest_city[@confidence $gt$ 40]” value=“//dest_city” /></sp:reco> </t:par> </body> </html>

APPENDIX B

[0631] 1 QA Speech Control

[0632] The QA control adds speech functionality to the primary controlto which it is attached. Its object model is an abstraction of thecontent model of the exemplary tags in Appendix A. 1.1 QA control  <Speech:QA     id=“...”     controlsToSpeechEnable=“...”    speechIndex=“...”     ClientTest=“...”     runat=“server” >    <Question ...>     <Statement ...>     ...     <Answer ...>    <Confirm ...>     ...     <Command ...>     ...   </Speech:QA>

[0633] 1.1.1 Core Properties

[0634] String ControlsToSpeechEnable

[0635] ControlsToSpeechEnable specifies the list of IDs of the primarycontrols to speech enable. IDs are comma delimited.

[0636] 1.1.2 Activation Mechanisms

[0637] int SpeechIndex

[0638] SpeechIndex specifies the ordering information of the QAcontrol—this is used by RunSpeech. Note: If more than one QA control hasthe same SpeechIndex, RunSpeech will execute them in source order. Insituations where some QA controls have SpeechIndex specified and some QAcontrols do not, RunSpeech will order the QA controls first bySpeechIndex, then by source order.

[0639] String ClientTest

[0640] ClientTest specifies a client-side script function which returnsa boolean value to determine when the QA control is considered availablefor selection by the RunSpeech algorithm. The system strategy cantherefore be changed by using this as a condition to activate orde-activate QA controls more sensitively than SpeechIndex. If notspecified, the QA control is considered available for activation.

[0641] 1.1.3 Questions, Statements, Answers, Confirms and Commands

[0642] Question[ ] Questions

[0643] QA control contains an array of question objects or controls,defined by the dialog author. Each question control will typicallyrelate to a function of the system, eg asking for a value, etc. Eachquestion control may specify an activation function using the ClientTestattribute, so an active QA control may ask different kinds of questionsabout its primary control under different circumstances. For example,the activation condition for main question Q_Main may be that thecorresponding primary control has no value, and the activation conditionfor a Q_GiveHelp may be that the user has just requested help. EachQuestion may specify answer controlss from within the QA control whichare activated when the question control is outputted.

[0644] Statement[ ] Statement

[0645] QA control contains an array of statement objects or controls.Statements are used to provide information to the listener, such aswelcome prompts.

[0646] Answer[ ] Answers

[0647] QA control contains an array of answer objects or controls. Ananswer control is activated directly by a question control within the QAcontrol, or by a StartEvent from the Primary control. Where multipleanswers are used, they will typically reflect answers to the systemfunctions, e.g. A_Main might provide a value in response to Q_Main, andA_Confirm might providing a yes/no+correction to Confirm.

[0648] Confirm[ ] Confirm

[0649] QA control may contain a confirm object or control. This objectis a mechanism provided to the dialog authors which simplify theauthoring of common confirmation subdialogs.

[0650] Command[ ] Command

[0651] A Command array holds a set of command controls. Command controlscan be thought of as answer controls without question controls, whosebehavior on recognition can be scoped down the control tree.

[0652] 1.2 Question Control

[0653] The question control is used for the speech output relating to agiven primary control. It contains a set of prompts for presentinginformation or asking a question, and a list of ids of the answercontrols, which may provide an answer to that question. If multipleanswer controls are specified, these grammars are loaded in parallelwhen the question is activated. An exception will be thrown if no answercontrol is specified in the question control. <Question id=“...”ClientTest=“...” Answers=“...” Count=“...” initialTimeout=“...”babbleTimeout=“...” maxTimeout=“...” Modal=“...” PromptFunction=“...”OnClientNoReco=“...” > <prompt ... /> ... </Question>

[0654] String ClientTest

[0655] ClientTest specifies the client-side script function returning aboolean value which determines under which circumstances a questioncontrol is considered active within its QA control (the QA controlitself must be active for the question to be evaluated). For a given QAcontrol, the first question control with a true condition is selectedfor output. For example, the function may be used to determine whetherto output a question which asks for a value (“Which city do you want?”)or which attempts to confirm it (“Did you say London?”). If notspecified, the question condition is considered true.

[0656] Prompt[ ] Prompts

[0657] The prompt array specifies a list of prompt objects, discussedbelow-Prompts are also able to specify conditions of selection (viaclient functions), and during RunSpeech execution only the first promptwith a true condition is selected for playback.

[0658] String Answers

[0659] Answers is an array of references by ID to controls that arepossible answers to the question. The behavior is to activate thegrammar from each valid answer control in response to the prompt askedby the question control.

[0660] Integer initialTimeout

[0661] The time in milliseconds between start of recognition and thedetection of speech. This value is passed to the recognition platform,and if exceeded, an onSilence event will be thrown from the recognitionplatform. If not specified, the speech platform will use a defaultvalue.

[0662] Integer babbleTimeout

[0663] The period of time in milliseconds in which the recognitionserver or other recognizer must return a result after detection ofspeech. For recos in “tap-and-talk” scenarios this applies to the periodbetween speech detection and the recognition result becoming available.For recos in dictation scenarios, this timeout applies to the periodbetween speech detection and each recognition return—i.e. the period isrestarted after each return of results or other event. If exceeded, theonClientNoReco event is thrown but different status codes are possible.If there has been any kind of recognition platform error that isdetectable and the babbleTimeout period has elapsed, then anonClientNoReco is thrown but with a status code −3. Otherwise if therecognizer is still processing audio—e.g. in the case of anexceptionally long utterance or if the user has kept the pen down for anexcessive amount of time—the onClientNoReco event is thrown, with statuscode −15. If babbleTimeout is not specified, the speech platform willdefault to an internal value.

[0664] Integer maxTimeout

[0665] The period of time in milliseconds between recognition start andresults returned to the client device browser. If exceeded, theonMaxTimeout event is thrown by the browser—this caters for network orrecognizer failure in distributed environments. For recos in dictationscenarios, as with babbleTimeout, the period is restarted after thereturn of each recognition or other event. Note that the maxTimeoutattribute should be greater than or equal to the sum of initialTimeoutand babbleTimeout. If not specified, the value will be a browserdefault.

[0666] Bool Modal

[0667] When modal is set to true, no answers except the immediate set ofanswers to the question are activated (i.e. no scoped Answers areconsidered). The defaults is false. For Example, this attribute allowsthe application developer to force the user of the client device toanswer a particular question.

[0668] String PromptFunction(Prompt)

[0669] PromptFunction specifies a client-side function that will becalled once the question has been selected but before the prompt isplayed. This gives a chance to the application developer to perform lastminute modifications to the prompt that may be required. PromptFunctiontakes the ID of the target prompt as a required parameter.

[0670] String OnClientNoReco

[0671] OnClientNoReco specifies the name of the client-side function tocall when the NoReco (mumble) event is received.

[0672] 1.2.1 Prompt Object

[0673] The prompt object contains information on how to play prompts.All the properties defined are read/write properties. <prompt id=“...”count=“...” ClientTest=“...” source=“...” bargeIn=“...”onClientBargein=“...” onClientComplete=“...” onClientBookmark=“...” > .. . text/markup of the prompt . . . </prompt>

[0674] Int Count

[0675] Count specifies an integer which is used for prompt selection.When the value of the count specified on a prompt matches the value ofthe count of its question control, the prompt is selected for playback.Legal values are 0-100. <Question id=Q_Ask”> <prompt count=“1”> Hello</prompt> <prompt count=“2”> Hello again </prompt> </Question>

[0676] In the example, when Q_Ask.count is equal to 1, the first promptis played, and if it is equal to 2 (i.e. the question has already beenoutput before), the second prompt is then played.

[0677] String ClientTest

[0678] ClientTest specifies the client-side script function returning aboolean value which determines under which circumstances a prompt withinan active question control will be selected for output. For a givenquestion control, the first prompt with a true condition is selected.For example, the function may be used to implement prompt tapering, eg(“Which city would you like to depart from?” for a function returningtrue if the user if a first-timer, or “Which city?” for an old hand). Ifnot specified, the prompt's condition is considered true.

[0679] String InlinePrompt

[0680] The prompt property contains the text of the prompt to play. Thisis defined as the content of the prompt element. It may contain furthermarkup, as in TTS rendering information, or <value>elements. As with allparts of the page, it may also be specified as script code within<script>tags, for dynamic rendering of prompt output.

[0681] String Source

[0682] Source specifies the URL from which to retrieve the text of theprompt to play. If an inline prompt is specified, this property isignored.

[0683] Bool BargeIn

[0684] BargeIn is used to specify whether or not barge-in (wherein theuser of the client device begins speaking when a prompt is being played)is allowed on the prompt. The defaults is true.

[0685] String onClientBargein

[0686] onClientBargein specifies the client-side script function whichis invoked by the bargein event.

[0687] String onClientComplete

[0688] onClientComplete specifies the client-side script function whichis invoked when the playing of the prompt has competed.

[0689] String OnClientBookmark

[0690] OnClientBookmark accesses the name of the client-side function tocall when a bookmark is encountered.

[0691] 1.2.2 Prompt Selection

[0692] On execution by RunSpeech, a QA control selects its prompt in thefollowing way:

[0693] ClientTest and the count attribute of each prompt are evaluatedin order. The first prompt with both ClientTest and count true isplayed. A missing count is considered true. A missing ClientTest isconsidered true.

[0694] 1.3 Statement Control

[0695] Statement controls are used for information-giving system outputwhen the activation of grammars is not required. This is common invoice-only dialogs. Statements are played only once per page if theplayonce attribute is true. <Statement id=“...” playOnce=“...”ClientTest=“...” PromptFunction=“...” > <prompt ... /> ... </Statement >

[0696] Bool playOnce

[0697] The playonce attribute specifies whether or not a statementcontrol may be activated more than once per page. playOnce is a Booleanattribute with a default (if not specified) of TRUE, i.e., the statementcontrol is executed only once. For example, the playOnce attribute maybe used on statement controls whose purpose is to output email messagesto the end user. Setting playOnce=“False” will provide dialog authorswith the capability to enable a “repeat” functionality on a page thatreads email messages.

[0698] String ClientTest

[0699] ClientTest specifies the client-side script function returning aboolean value which determines under which circumstances a statementcontrol will be selected for output. RunSpeech will activate the firstStatement with ClientTest equal to true. If not specified, theClientTest condition is considered true.

[0700] String PromptFunction

[0701] PromptFunction specifies a client-side function that will becalled once the statement control has been selected but before theprompt is played. This gives a chance to the authors to do last minutemodifications to the prompt that may be required.

[0702] Prompt[ ] Prompt

[0703] The prompt array specifies a list of prompt objects. Prompts arealso able to specify conditions of selection (via client functions), andduring RunSpeech execution only the first prompt with a true conditionis selected for playback. <Speech:QA id=“QA_Welcome”ControlsToSpeechEnable=“Label1” runat=“server” > <Statementid=“WelcomePrompt” > <prompt bargeIn=“False”> Welcome </prompt></Statement> </Speech:QA>

[0704] 1.4 Confirm Control

[0705] Confirm controls are special types of question controls. They mayhold all the properties and objects of other questions controls, butthey are activated differently. The RunSpeech algorithm will check theconfidence score found in the confirmThreshold of the answer control ofthe ControlsToSpeechEnable. If it is too low, the confirm control isactivated. If the confidence score of the answer control is below theconfirmThreshold, then the binding is done but the onClientReco methodis not called. The dialog author may specify more than one confirmcontrol per QA control. RunSpeech will determine which confirm controlto activate based on the function specified by ClientTest. <AnswerConfirmThreshold=... /> <Confirm> ...all attributes and objects ofQuestion... </Confirm>

[0706] 1.5 Answer Control

[0707] The answer control is used to specify speech input resources andfeatures. It contains a set of grammars related to the primary control.Note that an answer may be used independently of a question, inmultimodal applications without prompts, for example, or in telephonyapplications where user initiative may be enabled by extra-answers.Answer controls are activated directly by question controls, by atriggering event, or by virtue of explicit scope. An exception will bethrown if no grammar object is specified in the answer control. <Answerid=“...” scope=“...” StartEvent=“...” StopEvent=“...” ClientTest=“...”onClientReco=“...” onClientDTMF=“...” autobind=“...” server=“...”ConfirmThreshold=“...” RejectThreshold=“...” > <grammar ... /> <grammar... /> ... <dtmf ... /> <dtmf ... /> ... <bind ... /> <bind ... /> ...</Answer>

[0708] String Scope

[0709] Scope holds the id of any named element on the page. Scope isused in answer control for scoping the availability of user initiative(mixed task initiative: i.e. service jump digressions) grammars. Ifscope is specified in an answer control, then it will be activatedwhenever a QA control corresponding to a primary control within thesubtree of the contextual control is activated.

[0710] String StartEvent

[0711] StartEvent specifies the name of the event from the primarycontrol that will activate the answer control (start the Reco object).This will be typically used in multi-modal applications, eg onMouseDown,for tap-and-talk.

[0712] String StopEvent

[0713] StopEvent specifies the name of the event from the primarycontrol that will de-activate the answer control (stop the Reco object).This will be typically used in multi-modal applications, eg onMouseUp,for tap-and-talk.

[0714] String ClientTest

[0715] ClientTest specifies the client-side script function returning aboolean value which determines under which circumstances an answercontrol otherwise selected by scope or by a question control will beconsidered active. For example, the test could be used duringconfirmation for a ‘correction’ answer control to disable itself whenactivated by a question control, but mixed initiative is not desired(leaving only accept/deny answers controls active). Or a scoped answercontrol which permits a service jump can determine more flexible meansof activation by specifying a test which is true or false depending onanother part of the dialog. If not specified, the answer control'scondition is considered true.

[0716] Grammar[ ] Grammars

[0717] Grammars accesses a list of grammar objects.

[0718] DTMF[ ] DTMFs

[0719] DTMFs holds an array of DTMF objects.

[0720] Bind[ ] Binds

[0721] Binds holds a list of the bind objects necessary to map theanswer control grammar results (dtmf or spoken) into control values. Allbinds specified for an answer will be executed when the relevant outputis recognized. If no bind is specified, the SML output returned byrecognition will be bound to the control specified in theControlsToSpeechEnable of the QA control

[0722] String OnClientReco

[0723] OnClientReco specifies the name of the client-side function tocall when spoken recognition results become available.

[0724] String OnClientDTMF

[0725] OnClientDTMF holds the name of the client-side function to callwhen DTMF recognition results become available.

[0726] Boolean Autobind

[0727] The value of autobind determines whether or not the systemdefault bindings are implemented for a recognition return from theanswer control. If unspecified, the default is true. Setting autobind tofalse is an instruction to the system not to perform the automaticbinding.

[0728] String Server

[0729] The server attribute is an optional attribute specifying the URIof the speech server to perform the recognition. This attributeover-rides the URI of the global speech server attribute.

[0730] integer ConfirmThreshold

[0731] Holds a value representing the confidence level below which aconfirm control question will be automatically triggered immediatelyafter an answer is recognized within the QA control. Legal values are0-100.

[0732] Note that where bind statements and onClientReco scripts are bothspecified, the semantics of the resulting Tags are that binds areimplemented before the script specified in onClientReco.

[0733] integer RejectThreshold

[0734] RejectThreshold specifies the minimum confidence score toconsider returning a recognized utterance. If overall confidence isbelow this level, a NoReco event will be thrown. Legal values are 0-100.

[0735]1.5.1 Grammar

[0736] The grammar object contains information on the selection andcontent of grammars, and the means for processing recognition results.All the properties defined are read/write properties. <GrammarClientTest=“...” Source=“...”> ...grammar rules... </Grammar>

[0737] String ClientTest

[0738] The ClientTest property references a client-side boolean functionwhich determines under which conditions a grammar is active. If multiplegrammars are specified within an answer control (e.g. to implement asystem/mixed initiative strategy, or to reduce the perplexity ofpossible answers when the dialog is going badly), only the first grammarwith a true ClientTest function will be selected for activation duringRunSpeech execution. If this property is unspecified, true is assumed.

[0739] String Source

[0740] Source accesses the URI of the grammar to load, if specified.

[0741] String InlineGrammar

[0742] InlineGrammar accesses the text of the grammar if specifiedinline. If that property is not empty, the Source attribute is ignored.

[0743] 1.5.2 Bind

[0744] The object model for bind follows closely its counterpart clientside tags. Binds may be specified both for spoken grammar and for DTMFrecognition returns in a single answer control. <bind Value=“...”TargetElement=“...” TargetAttribute=“...” Test=“...” />

[0745] String Value

[0746] Value specifies the text that will be bound into the targetelement. It is specified as an XPath on the SML output from recognition.

[0747] String TargetElement

[0748] TargetElement specifies the id of the primary control to whichthe bind statement applies. If not specified, this is assumed to be theControlsToSpeechEnable of the relevant QA control.

[0749] String TargetAttribute

[0750] TargetAttribute specifies the attribute on the TargetElementcontrol in which bind the value. If not specified, this is assumed to bethe Text property of the target element.

[0751] String Test

[0752] The Test attribute specifies a condition which must evaluate totrue on the binding mechanism. This is specified as an XML Pattern onthe SML output from recognition.

[0753] 1.5.2.1 Automatic Binding

[0754] The default behavior on the recognition return to aspeech-enabled primary control is to bind certain properties into thatprimary control. This is useful for the dialog controls to examine therecognition results from the primary controls across turns (and evenpages). Answer controls will perform the following actions uponreceiving recognition results:

[0755] 1.bind the SML output tree into the SML attribute of the primarycontrol

[0756] 2. bind the text of the utterance into the SpokenText attributeof the primary control

[0757] 3. bind the confidence score returned by the recognizer into theConfidence attribute of the primary control.

[0758] Unless autobind=“False” attribute is specified on an answercontrol, the answer control will perform the following actions on theprimary control:

[0759] 1. bind the SML output tree into the SML attribute;

[0760] 2. bind the text of the utterance into the SpokenText attribute;

[0761] 3. bind the confidence score returned by the recognizer into theConfidence attribute;

[0762] Any values already held in the attribute will be overwritten.Automatic binding occurs before any author-specified bind commands, andhence before any onClientReco script (which may also bind to theseproperties).

[0763] 1.5.3 DTMF

[0764] DTMF may be used by answer controls in telephony applications.The DTMF object essentially applies a different modality of grammar (akeypad input grammar rather than a speech input grammar) to the sameanswer. The DTMF content model closely matches that of the client sideoutput Tags DTMF element. Binding mechanisms for DTMF returns arespecified using the targetAttribute attribute of DTMF object. <DTMFfirstTimeOut=“...” interDigitTimeOut=“...” numDigits=“...” flush=“...”escape=“...” targetAttribute=“...” ClientTest=“...”> <dtmfGrammar ...></DTMF>

[0765] integer firstTimeOut

[0766] The number of milliseconds to wait between activation and thefirst key press before raising a timeout event.

[0767] integer interDigitTimeOut

[0768] The number of milliseconds to wait between key presses beforeraising a timeout event.

[0769] int numDigits

[0770] The maximum number of key inputs permitted during DTMFrecognition.

[0771] Bool Flush

[0772] A flag which states whether or not to flush the telephonyserver's DTMF buffer before recognition begins. Setting flush to falsepermits DTMF key input to be stored between recognition/page calls,which permits the user to ‘type-ahead’.

[0773] String Escape

[0774] Holds the string value of the key which will be used to end DTMFrecognition (eg ‘#’).

[0775] String targetAttribute

[0776] TargetAttribute specifies the property on the primary control inwhich to bind the value. If not specified, this is assumed to be theText property of the primary control.

[0777] String ClientTest

[0778] The ClientTest property references a client-side boolean functionwhich determines under which conditions a DTMF grammar is active. Ifmultiple grammars are specified within a DTMF object, only the firstgrammar with a true ClientTest function will be selected for activationduring RunSpeech execution. If this property is unspecified, true isassumed.

[0779] 1.5.4 DTMFGrammar

[0780] DTMFGrammar maps a key to an output value associated with thekey. The following sample shows how to map the “1” and “2” keys to textoutput values. <dtmfgrammar>   <key value=“1”>Seattle</key>   <keyvalue=“2”>Boston</key> </dtmfgrammar>

[0781] 1.6 Command Control

[0782] The command control is a special variation of answer controlwhich can be defined in any QA control. Command controls are forms ofuser input which are not answers to the question at hand (eg, Help,Repeat, Cancel), and which do not need to bind recognition results intoprimary controls. If the QA control specifies an activation scope, thecommand grammar is active for every QA control within that scope. Hencea command does not need to be activated directly by a question controlor an event, and its grammars are activated in parallel independently ofanswer controls building process. Command controls of the same type atQA controls lower in scope can override superior commands withcontext-sensitive behavior (and even different/extended grammars ifnecessary). <Command   id=“...”   scope=“...”   type=“...”  RejectThreshold=“...”   onClientReco=“...” >   <Grammar ...>   <dtmf... >   ... </Command>

[0783] String Scope

[0784] Scope holds the id of a primary control. Scope is used in commandcontrols for scoping the availability of the command grammars. If scopeis specified for a command control, the command's grammars will beactivated whenever a QA control corresponding to a primary controlwithin the subtree of the contextual control is activated.

[0785] String Type

[0786] Type specifies the type of command (eg ‘help’, ‘cancel’ etc.) inorder to allow the overriding of identically typed commands at lowerlevels of the scope tree. Any string value is possible in thisattribute, so it is up to the author to ensure that types are usedcorrectly.

[0787] integer RejectThreshold

[0788] RejectThreshold specifies the minimum confidence level ofrecognition that is necessary to trigger the command in recognition(this is likely to be used when higher than usual confidence isrequired, eg before executing the result of a ‘Cancel’ command). Legalvalues are 0-100.

[0789] String onClientReco

[0790] onCommand specifies the client-side script function to execute onrecognition of the command control's grammar.

[0791] Grammar Grammar

[0792] The grammar object which will listen for the command.

[0793] DTMF DTMF

[0794] The dtmf object which will activate the command.

[0795] 2 Types of Initiatives and Dialog Flows

[0796] Using the control described above, various forms of initiativescan be developed, some examples are provided below:

[0797] 2.1 Mixed Initiative Dialogs

[0798] Mixed initiative dialogs provide the capability of acceptinginput for multiple controls with the asking of a single question. Forexample, the answer to the question “what are your travel plans” mayprovide values for an origin city textbox control, a destination citytextbox control and a calendar control (“Fly from Puyallup to Yakima onSeptember 30^(th)”).

[0799] A robust way to encode mixed initiative dialogs is to handwritethe mixed initiative grammar and relevant binding statements, and applythese to a single control.

[0800] The following example shows a single page used for a simple mixedinitiative voice interaction about travel. The first QA controlspecifies the mixed initiative grammar and binding, and a relevantprompt asking for two items. The second and third QA controls are notmixed initiative, and so bind directly to their respective primarycontrol by default (so no bind statements are required). The RunSpeechalgorithm will select the QA controls based on an attribure“SpeechIndex” and whether or not their primary controls hold validvalues. <%@ Page language=“c#” AutoEventWireup=“false”inherits=“SDN.Page” %> <%@ Register tagPrefix=“SDN” Namespace=“SDN”Assembly=“SDN” %> <html> <body> <Form id=“WebForm1” method=postrunat=“server”> <ASP:Label id=“Label1” runat=“server”>Departurecity</ASP:Label> <ASP:TextBox id=“TextBox1” runat=“server” /> <br><ASP:Label id=“Label2” runat=“server”>Arrival city</ASP:Label><ASP:TextBox id=“TextBox2” textchanged=“TextChanged” runat=“server” /><!-- speech information --> <Speech:QA id=“QAmixed”controlsToSpeechEnable=“TextBox1” speechIndex=“1” runat=“server”>  <Question id=“Q1” Answers=“A1”>     <prompt>“Please say the cities youwant to fly from and to”</prompt>   </Question>   <Answer id=“A1” >    <grammar src=“...”/>     <bind targetElement=“TextBox1”value=“/sml/path1”/>     <bind targetElement=“TextBox2”value=“/sml/path2”/>   </Answer> </Speech:QA> <Speech:QA id=“QA1”controlsToSpeechEnable=“TextBox1” speechIndex=“2” runat=“server”>  <Question id=“Q1” Answers=“A1”>     <prompt>“What's the departurecity?”</prompt>   </Question>   <Answer id=“A1”>     <grammarsrc=“...”/>   </Answer> </Speech:QA> <Speech:QA id=“QA2”controlsToSpeechEnable=“TextBox2” speechIndex=“3” runat=“server”>  <Question id=“Q1” Answer=“A1”>     <prompt>“What's the arrivalcity”</prompt>   </Question>   <Answer id=“A1” >     <grammarsrc=“...”/>   </Answer> </Speech:QA> </Form> </body> </html> 2.2 ComplexMixed Initiative Application developers can specify several answer tothe same question control with different levels of initiatives.Conditions are specified that will select one of the answers when thequestion is asked, depending on the initiative settings that theyrequire. An example is provided below:   <Speech:QA     id=“QA_Panel2”    ControlsToSpeechEnable=“Panel2”     runat=“server” >     <Question      answers=“systemInitiative, mixedInitiative” .../>     <Answer id=“systemInitiative”           ClientTest=“systemInitiativeCond”          onClientReco=“SimpleUpdate” >           <grammarsrc=“systemInitiative.gram” />     </Answer>     <Answer id=“mixedInitiative”           ClientTest=“mixedInitiativeCond”          onClientReco=“MixedUpdate” >           <grammarsrc=“mixedInitiative.gram” />     </Answer>   </Speech:QA>

[0801] Application developers can also specify several question controlsin a QA control. Some question controls can allow a mixed initiativestyle of answer, whilst others are more directed. By authoringconditions on these question controls, application developer can selectbetween the questions depending on the dialogue situation.

[0802] In the following example the mixed initiative question asks thevalue of the two textboxes at the same time (e.g., ‘what are your travelplans.?’) and calls the mixed initiative answer (e.g., ‘from London toSeattle’). If this fails, then the value of each textbox is askedseparately (e.g., ‘where do you leave from’ and ‘where are you goingto’) but, depending on the conditions, the mixed-initiative grammar maystill be activated, thus allowing users to provide both values.<Speech:QA   id=“QA_Panel2”   ControlsToSpeechEnable=“TextBox1,TextBox2”   runat=“server” >   <Question     ClientTest=“AllEmpty( )”    answers=“AnsAll”     .../>   <Question    ClientTest=“TextBox1IsEmpty( )”     answers=“AnsAll, AnsTextBox1”.../>   <Question     ClientTest=“TextBox2IsEmpty( )”    answers=“AnsAll, AnsTextBox2” .../>   <Answer     id=“AnsTextBox1”    onClientReco=“SimpleUpdate”>     <grammar src=“AnsTextBox1.gram” />  </Answer>   <Answer     id=“AnsTextBox2”    onClientReco=“SimpleUpdate” >     <grammar src=“ AnsTextBox2.gram”/>   </Answer>   <Answer     id=“AnsAll”    ClientTest=“IsMixedInitAllowed( )”     onClientReco=“MixedUpdate”    >     <grammar src=“AnsAll.gram” />   </Answer> </Speech:QA>

[0803] 2.3 User Initiative

[0804] Similar to the command control, a standard QA control can specifya scope for the activation of its grammars. Like a command control, thisQA control will activate the grammar from a relevant answer controlwhenever another QA control is activated within the scope of thiscontext. Note that its question control will only be asked if the QAcontrol itself is activated. <Speech:QA   id=“QA_Panel2”  ControlsToSpeechEnable=“Panel2”   runat=“server” >   <Question ... />  <Answer  id=“AnswerPanel2”         scope=“Panel2”        onClientReco=“UpdatePanel2( )” >     <grammar src=“Panel2.gram”/>   </Answer> </Speech:QA>

[0805] This is useful for dialogs which allow ‘service jumping’—userresponses about some part of the dialog which is not directly related tothe question control at hand.

[0806] 2.4 Short Time-Out Confirms

[0807] Application developers can write a confirmation as usual but seta short time-out. In the timeout handler, code is provided to thataccept the current value as exact.   <Speech:QA     id=“QA_Panel2”    ControlsToSpeechEnable=“Panel2”     runat=“server” >     <ConfirmtimeOut=“20” onClientTimeOut=“AcceptConfirmation”... />     <Answer id=“CorrectPanel2”           onClientReco=“UpdatePanel2( )” >      <grammar src=“Panel2.gram” />     </Answer>   </Speech:QA>

[0808] 2.5 Dynamic Prompt Building and Editing

[0809] The promptFunction script is called after a question control isselected but before a prompt is chosen and played. This lets applicationdevelopers build or modify the prompt at the last minute. In the examplebelow, this is used to change the prompt depending on the level ofexperience of the users. <script language=javascript>   functionGetPrompt( ) {     if(experiencedUser == true)       Prompt1.Text =“What service do you   want?”;     else       Prompt1.Text = “Pleasechoose between       e-mail,               calendar and news”;    return;   } </script> <Speech:QA   id=“QA_Panel2”    ControlsToSpeechEnable=“Panel2”     runat=“server” >     <QuestionPromptFunction=“GetPrompt”... >       <Prompt id=“Prompt1” />    </Question>     <Answer ... /> </Speech:QA>

[0810] 2.6 Using Semantic Relationships

[0811] Recognition and use of semantic relationships can be done bystudying the result of the recognizer inside the onReco event handler.<script language=“javascript”> function Reco( ) {   /*

[0812] Application developers can access the SML returned by therecogniser or recognition server. If a semantic relationship (likesport-news) is identified, the confidence of the individual elements canbe increased or take any other appropriate action.  */ } </script><Speech:QA   id=“QA_Panel2”   ControlsToSpeechEnable=“Panel2”  runat=“server” >   <Question ... />   <Answer onClientReco=“Reco” >    <grammar src=“Panel2.gram” />   </Answer> </Speech:QA>

[0813] 3 Implementation and Application of RunSpeech

[0814] A mechanism is needed to provide voice-only clients with theinformation necessary to properly render speech-enabled pages. Such amechanism must provide the execution of dialog logic and maintain stateof user prompting and grammar activation as specified by the applicationdeveloper.

[0815] Such a mechanism is not needed for multimodal clients. In themultimodal case, the page containing speech-enabled controls is visibleto the user of the client device. The user of the client device mayprovide speech input into any visible speech-enabled control in anydesired order using the a multimodal paradigm.

[0816] The mechanism used by voice-only clients to render speech-enabledpages is the RunSpeech script or algorithm. The RunSpeech script reliesupon the SpeechIndex attribute of the QA control and the SpeechGroupcontrol discussed below.

[0817] 3.1 SpeechControl

[0818] During run time, the system parses a control script or webpagehaving the server controls and creates a tree structure of servercontrols. Normally the root of the tree is the Page control. If thecontrol script uses custom or user control, the children tree of thiscustom or user control is expanded. Every node in the tree has an ID andit is easy to have name conflict in the tree when it expands. To dealwith possible name conflict, the system includes a concept ofNamingContainer. Any node in the tree can implement NamingContainer andits children lives within that name space.

[0819] The QA controls can appear anywhere in the server control tree.In order to easily deal with SpeechIndex and manage client siderendering, a SpeechGroup control is provided. The Speechgroup control ishidden from application developer.

[0820] One SpeechGroup control is created and logically attached toevery NamingContainer node that contain QA controls in its childrentree. QA and SpeechGroup controls are considered members of its directNamingContainer's SpeechGroup. The top level SpeechGroup control isattached to the Page object. This membership logically constructs atree—a logical speech tree—of QA controls and SpeechGroup controls.

[0821] For simple speech-enabled pages or script (i.e., pages that donot contain other NamingContainers), only the root SpeechGroup controlis generated and placed in the page's server control tree before thepage is sent to the voice-only client. The SpeechGroup control maintainsinformation regarding the number and rendering order of QA controls onthe page.

[0822] For pages containing a combination of QA control(s) andNamingContainer(s), multiple SpeechGroup controls are generated: oneSpeechGroup control for the page (as described above) and a SpeechGroupcontrol for each NamingContainer. For a page containingNamingContainers, the page-level SpeechGroup control maintains QAcontrol information as described above as well as number and renderingorder of composite controls. The SpeechGroup control associated witheach NamingContainer maintains the number and rendering order of QAswithin each composite.

[0823] The main job of the SpeechGroup control is to maintain the listof QA controls and SpeechGroups on each page and/or the list of QAcontrols comprising a composite control. When the client side markupscript (e.g. HTML) is generated, each SpeechGroup writes out aQACollection object on the client side. A QACollection has a list of QAcontrols and QACollections. This corresponds to the logical server sidespeech tree. The RunSpeech script will query the page-level QACollectionobject for the next QA control to invoke during voice-only dialogprocessing.

[0824] The page level SpeechGroup control located on each page is alsoresponsible for:

[0825] Determining that the requesting client is a voice-only client;and

[0826] Generating common script and supporting structures for all QAcontrols on each page.

[0827] When the first SpeechGroup control renders, it queries theSystem.Web.UI.Page.Request.Browser property for the browser string. Thisproperty is then passed to the RenderSpeechHTML and RenderSpeechScriptmethods for each QA control on the page. The QA control will then renderfor the appropriate client(multimodal or voice-only).

[0828] 3.2 Creation of SpeechGroup Controls

[0829] During server-side page loading, the onLoad event is sent to eachcontrol on the page. The page-level SpeechGroup control is created bythe first QA control receiving the onLoad event. The creation ofSpeechGroup controls is done in the following manner: (assume a pagecontaining composite controls)

[0830] Every QA control will receive onLoad event from run time code.onLoad for a QA:

[0831] Get the QA's NamingContainer N1

[0832] Search for SpeechGroup in the N1's children

[0833] If already exists, register QA control with this SpeechGroup.onLoad returns.

[0834] If not found:

[0835] Create a new SpeechGroup G1, inserts it into the N1's children

[0836] If N1 is not Page, find N1's NamingContainer N2

[0837] Search for SpeechGroup in N2's children, if exists, say G2, addG1 to G2. If not, create a new one G2, inserts in to N2's children

[0838] Recursion until the NamingContainer is the Page (top level)

[0839] During server-side page rendering, the Render event is sent tothe speech-enabled page. When the page-level SpeechGroup controlreceives the Render event, it generates client side script to includeRunSpeech.js and inserts it into the page that is eventually sent to theclient device. It also calls all its direct children to render speechrelated HTML and scripts. If a child is SpeechGroup, the child in turncalls its children again. In this manner, the server rendering happensalong the server side logical speech tree.

[0840] When a SpeechGroup renders, it lets its children (which can beeither QA or SpeechGroup) render speech HTML and scripts in the order oftheir SpeechIndex. But a SpeechGroup is hidden and doesn't naturallyhave a SpeechIndex. In fact, a SpeechGroup will have the sameSpeechIndex as its NamingContainer, the one it attaches to. TheNamingContainer is usually a UserControl or other visible control, andan author can set SpeechIndex to it.

[0841] 3.3 RunSpeech

[0842] The purpose of RunSpeech is to permit dialog flow via logic whichis specified in script or logic on the client. In one embodiment,RunSpeech is specified in an external script file, and loaded by asingle line generated by the server-side rendering of the SpeechGroupcontrol, e.g.:   <script language=“javascript”src=“/scripts/RunSpeech.js” />

[0843] The RunSpeech.js script file should expose a means for validatingon the client that the script has loaded correctly and has the rightversion id, etc. The actual validation script will be automaticallygenerated by the page class as inline functions that are executed afterthe attempt to load the file.

[0844] Linking to an external script is functionally equivalent tospecifying it inline, yet it is both more efficient, since browsers areable to cache the file, and cleaner, since the page is not clutteredwith generic functions.

[0845] 3.4 Events

[0846] 3.4.1 Event Wiring

[0847] Tap-and-talk multimodality can be enabled by coordinating theactivation of grammars with the onMouseDown event. The wiring script todo this will be generated by the Page based on the relationship betweencontrols (as specified in the ControlsToSpeechEnable property of the QAcontrol in).

[0848] For example, given an asp:TextBox and its companion QA controladding a grammar, the <input> and <reco> elements are output by eachcontrol's Render method. The wiring mechanism to add the grammaractivation command is performed by client-side script generated by thePage, which changes the attribute of the primary control to add theactivation command before any existing handler for the activation event:<!-- Control output --> <input id=“TextBox1” type=“text” .../> <recoid=“Reco1” ... />   <grammar src=“...” /> </reco> <!-- Page output --><script>   TextBox1.onMouseDown = “Reco1.Start();”+TextBox1.onMouseDown; </script>

[0849] By default, hook up is via onmousedown and onmouseup events, butboth StartEvent and StopEvent can be set by web page author.

[0850] The textbox output remains independent of this modification andthe event is processed as normal if other handlers were present.

[0851] 3.4.2 Page Class Properties

[0852] The Page also contains the following properties which areavailable to the script at runtime:

[0853] SML—a name/value pair for the ID of the control and it'sassociated SML returned by recognition.

[0854] SpokenText—a name/value pair for the ID of the control and it'sassociated recognized utterance

[0855] Confidence—a name/value pair for the ID of the control and it'sassociated confidence returned by the recognizer.

[0856] 4 RunSpeech Algorithm

[0857] The RunSpeech algorithm is used to drive dialog flow on theclient device. This may involve system prompting and dialog management(typically for voice-only dialogs), and/or processing of speech input(voice-only and multimodal dialogs). It is specified as a script filereferenced by URI from every relevant speech-enabled page (equivalent toinline embedded script).

[0858] Rendering of the page for voice only browsers is done in thefollowing manner:

[0859] The RunSpeech module or function works as follows (RunSpeech iscalled in response to document.onreadystate becoming “complete”):

[0860] (1) Find the first active QA control in speech index order(determining whether a QA control is active is explained below).

[0861] (2) If there is no active QA control, submit the page.

[0862] (3) Otherwise, run the QA control.

[0863] A QA control is considered active if and only if:

[0864] (1) The QA control's ClientTest either is not present or returnstrue, AND

[0865] (2) The QA control contains an active question control orstatement control (tested in source order), AND

[0866] (3) Either:

[0867] a. The QA control contains only statement controls, OR

[0868] b. At least one of the controls referenced by the QA control'sControlsToSpeechEnable has an empty or default value.

[0869] A question control is considered active if and only if:

[0870] (1) The question control's ClientTest either is not present orreturns true, AND

[0871] (2) The question control contains an active prompt object.

[0872] A prompt object is considered active if and only if:

[0873] (1) The prompt object's ClientTest either is not present orreturns true, AND

[0874] (2) The prompt object's Count is either not present, or is lessthan or equal to the Count of the parent question control.

[0875] A QA control is run as follows:

[0876] (1) Determine which question control or statement control isactive and increment its Count.

[0877] (2) If a statement control is active, play the prompt and exit.

[0878] (3) If a question control is active, play the prompt and startthe Recos for each active answer control and command control.

[0879] An answer control is considered active if and only if:

[0880] (1) The answer control's ClientTest either is not present orreturns true, AND

[0881] (2) Either:

[0882] a. The answer control was referenced in the active questioncontol's Answers string, OR

[0883] b. The answer control is in Scope

[0884] A command control is considered active if and only if:

[0885] (1) It is in Scope, AND

[0886] (2) There is not another command control of the same Type lowerin the scope tree.

[0887] RunSpeech relies on events to continue driving the dialog—asdescribed so far it would stop after running a single QA control. Eventhandlers are included for Prompt.OnComplete, Reco.OnReco,Reco.OnSilence, Reco.OnMaxTimeout, and Reco.OnNoReco. Each of these willbe described in turn.

[0888] RunSpeechOnComplete works as follows:

[0889] (1) If the active Prompt object has an OnClientComplete functionspecified, it is called.

[0890] (2) If the active Prompt object was contained within a statementcontrol, or a question control which had no active answer controls,RunSpeech is called.

[0891] RunSpeechOnReco works as follows:

[0892] (1) Some default binding happens—the SML tree is bound to the SMLattribute and the text is bound to the SpokenText attribute of eachcontrol in ControlsToSpeechEnable.

[0893] (2) If the confidence value of the recognition result is belowthe ConfidenceThreshold of the active answer control, the Confirmationlogic is run.

[0894] (3) Otherwise, if the active answer control has on OnClientRecofunction specified, it is called, and then RunSpeech is called.

[0895] RunSpeechOnReco is responsible for creating and setting the SML,SpokenText and Confidence properties of the ControlsToSpeechEnable. TheSML, SpokenText and Confidence properties are then available to scriptsat runtime.

[0896] RunSpeechOnSilence, RunSpeechOnMaxTimeout, and RunSpeechOnNoRecoall work the same way:

[0897] (1) The appropriate OnClientXXX function is called, if specified.

[0898] (2) RunSpeech is called.

[0899] Finally, the Confirmation logic works as follows:

[0900] (1) If the parent QA control of the active answer controlcontains any confirm controls, the first active confirm-control is found(the activation of a confirm control is determined in exactly the sameway as the activation of a question control).

[0901] (2) If no active confirm control is found, RunSpeech is called.

[0902] (3) Else, the QA control is run, with the selected confirmcontrol as the active question control.

[0903] For multi-modal browsers, only the grammar loading and eventdispatching steps are carried out.

APENDIX C

[0904] 1 Design Principles

[0905] In this embodiment, there is no concept of primary control tospeech-enable as it existed in Appendix B. The speech layer providesinput to the visual layer as well as explicit support for dialog flowmanagement. The semantic layer implements the logic needed forconfirmation and validation. In a multimodal interaction, the semanticlayer does not need to be used as confirmation and validation are visualand implemented using standard ASP.NET constructs. If desired though,the sematic layer can be updated with value changes made through visualor GUI interfaces in order that confirmation and validation can be stillimplemented.

[0906]FIG. 13 illustrates the speech controls inheritance diagram.

[0907] 2 Authoring Scenarios

[0908] The following provides examples of various forms of applicationscenarios.

[0909] 2.1 Multimodal app, Tap-And-Talk <speech:QA id=“qa1”runat=“server”>   <Answers>     <speech:Answer SemanticItem=“siText”ID=“answer1”     XpathTrigger=“/sml/value”  runat=“server”>    </speech:Answer>   </Answers>   <RecoStartEvent=“textbox1.onmousedown”   StopEvent=“textbox1.onmouseup”ID=“reco1”   Mode=“Single”>     <Grammars>       <speech:Grammar      Src=“http://mysite/mygrammar.grxml”       ID=“Grammar1”runat=“server”>       </speech:Grammar>     </Grammars>   </Reco></speech:QA>

[0910] 2.2 Multimodal app, Click-And-Wait-For-Recognition <speech:QAid=“qa1” runat=“server”>   <Reco id=“reco1”StartEvent=“textbox1.onmousedown” mode=“automatic”>     <Grammars>      <speech:grammar   src=“htp://mysite/mygrammar.grxml”        rnat=“server”></speech:grammar>     </Grammars>   </Reco>  <Answers>     <speech:answer id=“answer1” XpathTrigger=“/sml/value”SemanticItem=“siText”   runat=“server”>     </speech:answer>  </Answers> </speech:QA>

[0911] 2.3 Multimodal app, Do-Field <speech:QA id=“qa1” runat=“server”>  <Reco id=“reco1” StartEvent=“dofieldButton.onmousedown”    StopEvent=“dofieldButton.onmouseup” mode=“multiple”>     <Grammars>      <speech:grammar src=“http://mysite/mylargegrammar.xml”runat=“server”>       </speech:grammar>     </Grammars>   </Reco>  <Answers>     <speech:answer id=“answer1” XpathTrigger=“/sml/value1”SemanticItem=“siOne”   runat=“server”>     </speech:answer>    <speech:answer id=“answer2” XpathTrigger=“/sml/value2”SemanticItem=“siTwo”   runat=“server”>     </speech:answer>    speech:answer id=“answer3” XpathTrigger=“/sml/value3”SemanticItem=“siThree”     runat=“server”>     </speech:answer>    <speech:answer id=“answer4” XpathTrigger=“/sml/value4”SemanticItem=“siFour”   runat=“server”>     </speech:answer>    <speech:answer id=“answer5” XpathTrigger=“/sml/value5”SemanticItem=“siFive”   runat=“server”>     </speech:answer>  </Answers> </speech:QA>

[0912] 2.4 Voice Only app, Statement <speech:QA id=“welcome”PlayOnce=“true” runat=“server”>   <Prompt InLineprompt=“Hellothere!”></Prompt> </speech:QA>

[0913] 2.5 Voice Only app, Simple Question <speech:QA id=“qa1”runat=“server”>   <Reco id=“reco1” mode=“automatic”>     <Grammars>      <speech:grammar src=“http://mysite/citygrammar.grxml”runat=“server”></speech:grammar>     </Grammars>   </Reco>   <PromptInLinePrompt=“Which city do you want to fly to?”></Prompt>   <Answers>    <speech:answer id=“answer1” XpathTrigger=“/sml/city”SemanticItem=“siCity” runat=“server”>     </speech:answer>   </Answers></speech:QA>

[0914] 2.6 Voice Only app, Question with Mixed-Initiative (OptionalAnswers) <speech:QA id=“qa1” runat=“server”>   <Reco id=“reco1”mode=“automatic”>     <Grammars>       <speech:grammarsrc=“http://mysite/cityANDstate.xml” runat=“server”></speech:grammar>    </Grammars>   </Reco>   <Prompt InLinePrompt=“Which city do you wantto fly to?”></Prompt>   <Answers>     <speech:answer id=“answer1”XpathTrigger=“/sml/city” SemanticItem = “siCity” runat=“server”>    </speech:answer>   </Answers>   <ExtraAnswers>     <speech:answerid=“answer2” XpathTrigger=“/sml/state” SemanticItem = “siState”runat=“server”>     </speech:answer>   </ExtraAnswers> </speech:QA>

[0915] 2.7 Voice Only app, Explicit Confirmation <speech:QA id=“qa1”runat=“server”>   <Reco id=“reco1” mode=“automatic”>     <Grammars>      <speech:grammar src=“http://mysite/citygrammar.xml”runat=“server”>       </speech:grammar>     </Grammars>   </Reco>  <Prompt InLinePrompt=“Which city do you want to fly to?”></Prompt>  <Answers>     <speech:answer id=“answer1” XpathTrigger=“/sml/city”SemanticItem=“siCity” confirmThreshold=“0.75”    runat=“server”>    </speech:answer>   </Answers> </speech:QA> <speech:QA id=“qa2”runat=“server” xpathAcceptConfirms=“/sml/accept”xpathDenyConfirms=“/sml/deny”>   <Prompt InLinePrompt=“Did you say<SALT:value>textbox1.value</SALT:value>”></Prompt>   <Reco id=“reco1”mode=“automatic”>     <Grammars>       <speech:grammarsrc=“http://mysite/yes_no_city.xml” runat=“server”></speech:grammar>    </Grammars>   </Reco>   <Confirms>     <speech:answer id=“answer2”XpathTrigger=“/sml/city” SemanticItem=“siCity”confirmThreshold=“0.75”    runat=“server”>     </speech:answer>  </Confirms> </speech:QA>

[0916] 2.8 Voice Only app, Short Time-Out Confirmation <speech:QAid=“qa1” runat=“server” xpathAcceptConfirms=“/sml/accept”xpathDenyConfirms=“/sml/deny”   firstInitialTimeout=“500”>   <PromptInLinePrompt=“Did you say<SALT:value>textbox1.value</SALT:value>”></Prompt>   <Reco id=“reco1”InitialTimeout=“350” mode=“automatic”>     <Grammars>      <speech:grammar src=“http://mysite/yes_no_city.grxml”runat=“server”></speech:grammar>     </Grammars>   </Reco>   <Confirms>    <speech:answer XpathTrigger=“/sml/city” SemanticItem=“siCity”confirmThreshold=“0.75”     runat=“server”>     </speech:answer>  </Confirms> </speech:QA>

[0917] 2.9 Voice Only app, Commands <speech:QA id=“qa1” runat=“server”>  <Prompt id=“prompt1” InLinePrompt=“Where do you want to flyto?”></Prompt>   <Reco id=“reco1” mode=“automatic”>     <Grammars>      <speech:grammar src=“http://mysite/city.grxml”      runat=“server”></speech:grammar>     </Grammars>   </Reco>  <Answers>     <speech:answer id=“answer1” XpathTrigger=“/sml/city”SemanticItem=“siCity” runat=“server”></speech:answer>   </Answers></speech:QA> <speech:Command id=“command1” type=“cancel” scope=“qa1”OnClientCommand=“myCommand”   runat=“server”></speech:Command> <script>  function myCommand( )   {  CallControl.HangUp( ); } </script>

[0918] 2.10 Voice Only app, Prompt Selection <speech:QA id=“qa1”runat=“server”>   <Prompt id=“prompt1” InLinePrompt=“Where do you wantto fly to?”></Prompt>   <Reco id=“reco1” mode=“automatic”>    <Grammars>       <speech:grammar src=“http://mysite/city.grxml”runat=“server”></speech:grammar>     </Grammars>   </Reco>   <Answers>    <speech:answer id=“answer1” XpathTrigger=“/sml/city”SemanticItem=“siCity”         runat=“server”></speech:answer>  </Answers> </speech:QA> <speech:Command id=“command1” type=“cancel”scope=“qa1” OnClientCommand=“myCommand”  runat=“server”></speech:Command> <script>   function myCommand( )  {  CallControl.Hangup( ); } </script> <speech:qa id=“qa1”runat=“server”>   <Prompt id=“prompt1”PromptSelectFunction=“promptSelection” />   <Reco id=“reco1”mode=“automatic”>     <Grammars>       <speech:grammarsrc=“http://mysite/city.xml” runat=“server”></speech:grammar>    </Grammars>   </Reco>   <Answers>     <speech:answer id=“answer1”XpathTrigger=“/sml/city” SemanticItem=“siCity”        runat=“server”></speech:answer>   </Answers> </speech:qa><script> function promptSelection (lastCommandOrException, count,answerArray) {   if (lastCommandOrException == “Silence”)    {    return “Sorry, I couldn't hear you. Please speak louder. Where doyou want to fly to?”;    }   else if (count>3)    {     return“Communication problems are preventing me from hearing the arrival city.Please try again later.”;    }     return “Where do you want to flyto?”; //Default prompt    } } </script>

[0919] 2.11 Voice Only app, Implicit Confirmation <speech:qa id=“qa1”runat=“server” xpathDenyConfirms=“/sml/deny”xpathAcceptConfirms=“/sml/accept”> <Prompt id=“prompt1”  PromptSelectFunction=“promptSelection”></Prompt> <Reco id=“reco1”mode=“automatic”>   <Grammars>       <speech:grammarsrc=“http://mysite/yes_no_city.xml” runat=“server”></speech:grammar>    </Grammars>   </Reco>   <Answers>     <speech:answer id=“answer1”XpathTrigger=“/sml/date” SemItem=“siDate”      runat=“server”></speech:answer>   </Answers>   <Confirms>    <speech:answer id=“confirm1” XpathTrigger=“/sml/city”SemItem=“siCity”       runat=“server”></speech:answer>   </Confirms></speech:qa> <script> function promptSelection (lastCommandOrException,count, SemanticItemList) {   var myPrompt = “”; if(SemanticItemList[“siCity”].value != null) {   myPrompt = “Flying from” + SemanticItemList[“siCity”].value + “. ”; myPrompt += “On whatdate?”; } else { myPrompt = “On what date?”; }   return myPrompt; }</script>

[0920] 2.12 Voice Only app, QA with reco and dtmf <speech:qa id=“qa1”runat=“server”>   <Prompt id=“prompt1” InLinePrompt=“Press or say one ifyou accept the charges, two       if you don't.”></Prompt>   <Recoid=“reco1” mode=“automatic”>     <Grammars>       <speech:grammarsrc=“http://mysite/acceptCharges.xml”    runat=“server”></speech:grammar>     </Grammars>   </Reco>   <DtmfsmlContext=“sml/accept”></Dtmf>   <Answers>     <speech:answerid=“answer1” XpathTrigger=“/sml/accept”   SemanticItem=“siAccept”runat=“server”></speech:answer>   </Answers> </speech:qa>

[0921] 2.13 Voice-Only app, Record-Only QA <speech:qa id=“qa1”runat=“server”>   <Answers>     <speech:answer id=“a1”XpathTrigger=“/SML/@recordlocation”     SemanticItem = “foo”runat=“server”></speech:answer>   </Answers>   <Reco id=“recordonly”>    <record beep=“true”></record>   </Reco> </speech:qa></FORM>

[0922] 3 Design Details

[0923] 3.1 QA Activation (Voice-Only)

[0924] QA are tested for activeness in SpeechIndex order (see run-timebehavior).

[0925] A QA is active when clientActivationFunction returns true AND

[0926] If the Answers array is non empty, the SemanticItems pointed toby the set of Answers are empty OR If the answers array is empty, atleast one item in the Confirm array does need confirmation

[0927] A QA can have only Answers (normal question: Where do you want togo?), only Confirms (explicit confirmation: Did you say Boston? or shorttime-out confirmation: Boston.), both (implicit confirmation: When doyou want to fly to Boston?) or none (statement: Welcome to myapplication!).

[0928] A QA can have extra answers even if it has no answers (e.g.,mixed initiative).

[0929] 3.2 Answer, Confirm.

[0930] Upon recognition, commands are processed first, followed byAnswers, ExtraAnswers and Confirms.

[0931] A target element (e.g. textbox1.value) can be in one of thesestates: empty, invalid, needsConfirmation, confirmed. A target is emptybefore any recognition result is associated with this item, or if theitem has been cleared. A target is in needsConfirmation state when arecognition result has been associated with it, but the confidence levelis below the confirmationThreshold for this item. And a target isconfirmed when either a recognition result has been associated with itwith a confidence level high enough or a confirmation loop set it tothis state explicitly.

[0932] Answers are therefore responsible for setting the value in thetarget element and the confidence level (this is done in a semanticlayer). Confirms are responsible for confirming the item, clearing it orsetting it to a new value (with a new confidence level).

[0933] 3.3 Command Execution (and Scope)

[0934] Commands specify a scope and are active for all QA's within thatscope. The default processing of a command is to set the current QA'slastCommandException to the command's type. If the command specifies aGrammar, this grammar is activated in parallel with any grammars in thecurrent Reco object. QAs can be modal (allowCommands=false), in whichcase, no commands will be processed for that particular QA.

[0935] 3.4 Validators

[0936] A CompareValidator will be active when the value of theSemanticItemToValidate it refers to has not been validated by thisvalidator. If SemanticItemToCompare is specified (rather thanValueToCompare), then the CompareValidator will only be active if thevalue of the SemanticItemToCompare is non-empty (i.e. if it has beenassigned a value by a previous QA).

[0937] A CustomValidator will be active when the value of theSemanticItemToValidate it refers to has not been validated by thisvalidator.

[0938] 4 Run Time Behavior

[0939] 4.1 Client Detection

[0940] The speech controls do pay attention to the variety of clientthat they are rendering for. If the client doesn't support SALT, thecontrols won't render any speech-related tags or script. Clientdetection is done by checking the browser capabilities and detectingwhether it's a voice-only client (browser is Quadrant), or multimodal(IE, PocketIE, etc, with SALT support).

[0941] Hands-free is not a mode in the client, but rather anapplication-specific modality, and therefore the only support requiredis SALT (as in multimodal). Hands-free operation is thereforeswitched-on by application logic. 4.2 Multimodal

[0942] Support for multimodal applications is built in the speechcontrols. In multimodal operations commands, dtmf, confirm, prompts, etcdo not make sense from an interaction point of view, so they won't berendered. Tap-and-talk (or any other type of interaction, likeclick-and-wait-for-recognition) is enabled by hooking up the calls tostart and stop recognition with GUI events using the Reco objectattributes startElement/startEvent and stopElement/stopEvent, plus theReco object mode attribute.

[0943] During render time, the speech controls are passed informationspecifying whether the client is a voice-only client or multmodalclient. If the client is multimodal, the rendering process hooks thecall to start recognition to the GUI event specified by the StartEventattribute of the Reco object. The rendering process also hooks the callto stop recognition to the GUI event specified by the StopEventattribute of the Reco object.

[0944] The multimodal client needs a mechanism which will invokeauthor-specified functions to handle speech-related events (e.g.,timeouts) or recognition processing. This mechanism is the Multimodal.jsscript. Multimodal.js is specified in an external script file and loadedby a single line generated by server-side rendering, e.g.,   <scriptlanguage=‘“javascript” src=“/scripts/Multimodal.js” />

[0945] This method mirrors the ASP.NET way of generating ‘system’client-side script loaded via URI. Linking to an external script isfunctionally equivalent to specifying it inline, yet is more efficientsince clients are able to cache the file, and cleaner, since the page isnot clutered with generic functions.

[0946] 4.3 Voice-Only

[0947] 4.3.1 Runtime Script (RunSpeech)

[0948] Unlike in a multimodal interaction, where the user initiates allspeech input by clicking/selecting visual elements in the GUI, amechanism is needed to provide voice-only clients with the informationnecessary to properly render speech-enabled ASP.NET pages. Such amechanism must guarantee the execution of dialog logic and maintainstate of user prompting and grammar activation as specified by theauthor.

[0949] The mechanism used by the Speech Controls is a client-side script(RunSpeech.js) that relies upon the SpeechIndex attribute of the QAcontrol, plus the flow control mechanisms built in the framework(ClientActivationFunction, default activation rules, etc.). RunSpeech isloaded via URI similar to the loading mechanism of Multimodal.js asdescribed above.

[0950] 4.3.2 SpeechIndex

[0951] SpeechIndex is an absolute ordering index within a namingcontainer.

[0952] If more than one speech control has the same SpeechIndex, theyare activated in source order. In situations where some controls haveSpeechIndex specified and some controls do not, those with SpeechIndexwill be activated first, then the rest in source order.

[0953] NOTE: Speech index is automatically set to 0 for new controls.Dialog designers should leave room in their numbering scheme to insertnew QA's later. Begin with a midrange integer and increment by 100, forexample. For example number QA's 1000, 1100, 1200 instead of 1, 2, 3.this leaves room for a large number of QA's at any point the dialog andplenty of room to add QA's at the beginning.

[0954] 4.3.3 ClientActivationFunction

[0955] clientActivationFunction specifies a client-side script functionwhich returns a boolean value to determine when this control isconsidered available for selection by the run-time control selectionalgorithm. If not specified, it defaults to true (control is active).

[0956] The system strategy can therefore be changed by using this as acondition to activate or de-activate QAs more sensitively thanSpeechIndex. If not specified, the QA is considered available foractivation.

[0957] 4.3.4 Count

[0958] Count is a property of the QA control that indicates how manytimes that control has been activated consecutively. This Count propertywill be reset if the previously active QA is different that the currentQA (same applies for Validators), otherwise, it is incremented by one.The Count property is exposed to application developers through thePromptSectionFunction of the Prompt object.

[0959] Controls Reference

[0960] General Authoring Notes

[0961] 1. Script References are not Validated at Render Time.

[0962] The Speech Controls and objects described in this section containattributes whose values are references to script functions written bythe dialog author. These functions are executed on client devices inresponse to speech-related events (e.g. expiration of timeout) or as runtime processing (e.g. modification of prompt text prior to playback).Render time validation is not performed on script references, i.e., nochecks for existence of script functions is done during rendering ofcontrols. If an attribute contains a reference to a client-side scriptfunction and the function does not exist, client-side exceptions will bethrown.

[0963] In voice-only mode, script functions generating exceptions duringruntime will cause a redirection to the error page defined in theWeb.config file. If no error page is defined, RunSpeech will continue toexecute without reporting the exception.

[0964] 2. All Speech Controls should be contained within ASP.NET <Form>Tag or Equivalant.

[0965] The Speech Control described in this section must all be placedin ASP.NET web pages inside the <form> tag. Behavior of controls placedoutside the <form> tag is undefined.

[0966] 3. Client-Side Script References must Refer to Function and notInclude Parenthes.

[0967] Using the PromptSelectFunction as an example. the following iscorrect syntax: <Prompt id=“P1” PromptSelectFunction=“mySelectFunction”/> //using “mySelectFunction( )” is incorrect syntax

[0968] 4. IE Requires Exact Cases when Running Jscript.

[0969] Therefore, the case for event values specified in the StartEventand StopEvent attributes of the Prompt object must be exactly as thoseevents are defined. This happens to be all lowercase letters for moststandard IE events. For example, the onmouseup and onmousedown eventsmust be specified in all lowercase letters.

[0970] 5. All Speech Controls Expose the Common Attribute id.

[0971] 6. Behavior of Visible and Enabled Properties of Speech Controls.

[0972] Setting the visible or enabled properies of Speech Controls to“False” will cause them not to render.

[0973] 7. Mimimum Client Requirements

[0974] In one embodiment, clients must be running IE6.0 or greater andJScript 5.5 or greater for speech controls and associated scriptfunctions to work properly.

[0975] 8. Rendering <smex> to Telserver

[0976] The speech controls automatically handle rendering <smex> tags tothe telephony server on every page as is required by the server. In oneembodiiment, smex tags are rendered whether the client is the tel serveror the desktop client.

[0977] 5 Global Application Settings

[0978] Speech Controls provide mechanisms that allow dialog authors tospecify values to control properties on an application or page basis.

[0979] 5.1 Application-Level Settings

[0980] 5.1.1 Application Global Variables

[0981] Dialog authors may use their application's Web.config file to setvalues of global variables for speech-enabled web applications. Thevalues of the global variables persist throughout the entrie lifetime ofthe web application. ‘Errorpage’ is the only global variable that may bespecified and is set for the application during render time.<appSettings>   <add key=“errorpage” value=“...” /> </appSettings>

[0982] The <appsettings> tag must be placed one level inside the<configuration> tag within the Web.config file.

[0983] The errorpage key specifies a URI to a default error page.Redirection to this error page will occur during run time when thespeech platform or the DTMF engine returns an error. A default errorpage is included with the SDK; the user can also create a custom errorpage.

[0984] Note: Developers who create their own error page must callwindow.close at the bottom of the error page in the voice only case inorder to release the call.

[0985] 5.1.2 Application-Level Setting of Common Control Properties

[0986] Dialog authors may use their application's Web.config file to setvalues of common control properties and have those values persist duringthe lifetime of the web application. For example, an author may wish usethe Web.config file to set the maxTimeout value for Reco objects intheir application. The properties are set in the Web.config file usingthe following syntax: <configuration>   <SpeechStyleSheet>     <Styleid=“style1” >       <QA allowCommands=“false”>       ...         <Promptbargein=“false” ... />         <Reco maxTimeout=“5000”... />        <Dtmf preFlush=“true” ... />         <AnswersconfirmThreshold=“0.80” ... />         <ExtraAnswersconfirmThreshold=“0.80” .../>         <ConfirmsconfirmThreshold=“0.80”... />       </QA>       <Command .../>      <CustomValidator .../>       <CompareValidator .../>      <SemanticItem .../>     </Style>   </SpeechStyleSheet></configuration>

[0987] The Reco corresponding Reco object would reference the “stylel”Style:

[0988] <Reco id=“recol” . . . StyleReference=“stylel” . . . />

[0989] If the Style id is “globalstyle,” the property values set in theStyle apply application-wide to pertinent controls. So, in the aboveexample, if id=“ ” (or the property is omitted from the Style tag), amaxTimeout of 5000 milliseconds will be used for all Reco objects in theapplication (uless overridden).

[0990] For a complete list of properties which are settable through theSpeechStyleSheet, see below.

[0991] 6 StyleSheet Control

[0992] The StyleSheet control allows dialog authors to set values tocommon control properties at a page-level scope. The StyleSheet controlis a collection of Style objects. The Style object exposes properties ofeach control that are settable on a page-level basis. The StyleSheetcontrol is rendered for both multimodal and voice-only modes. Anexception will be thrown if the StyleSheet control contains an objectwhich is not a Style object. class StyleSheet : SpeechControl {  string    id{get; set;};   StyleCollection  Styles{get;}; }

[0993] 6.1 StyleSheet Properties

[0994] Styles

[0995] Optional. Used in both multimodal and voice-only modes. TheStyles property is a collection of Style objects used to set propertyvalues for Speech Controls and their objects. The property values lastduring the lifetime of the current page.

[0996] 7 Style Object

[0997] The Style object is used to set property values for SpeechControls and their objects. The property values last during the lifetimeof the current page. class Style : Control {   string id{get; set;};  string StyleReference{get; set;};   QAStyle QA{get; set;};  CommandStyle Command{get; set;};   CustomValidatorStyleCustomValidator{get; set;};   CompareValidatorStyleCompareValidator{get; set;};   SemanticItemStyle SemanticItem{get;set;}; }

[0998] 7.1 Style Properties

[0999] id

[1000] Required. The programmatic name of the Style object.

[1001] StyleReference

[1002] Optional. Used in both multimodal and voice-only modes. Specifiesthe name of a Style object. At render time, the StyleSheet control willsearch for the named Style object and also set property values specifiedin the named Style. An exception is thrown for an invalidStyleReference.

[1003] For every property of a speech control with a StyleReference, thevalue is determined as follows:

[1004] 1. the value is set directly in the speech control

[1005] 2. the style object directly referenced

[1006] 3. any style referenced by a style

[1007] 4. the global style object

[1008] 5. the speech control default value.

[1009] The following example sets shows two QA properties are set usingStyleReference: <speech:StyleSheet id=“SS”>   <speech:Styleid=“base_style” >     <QA OnClientActive=“myOnClientActive”/>  </speech:Style>   <speech:Style id=“derived_style”StyleReference=“base_style”>     <QA PlayOnce=“true”/>   </speech:Style></speech:StyleSheet>

[1010] QA

[1011] Optional. The QA property of the Style object is used to setproperty values for all QA controls on a page that reference this Style.The following example shows how to set the AllowCommands and PlayOnceproperties for the QA controls that reference this Style:<speech:StyleSheet id=“SS1”>   <speech:Style id=“WelcomePageQA_Style” >    <QA AllowCommands=“false” PlayOnce=“true”/>   </speech:Style></speech:StyleSheet> <QA id=“...” StyleReference=“WelcomePageQA_Style”.../> The next example shows how to set the bargein property of allPrompt objects on a given page using Params: <speech:StyleSheetid=“SS2”> <Style Name=“Style1”>   <QA>    <AnswersConfirmThreshold=“0.8” Reject=“0.4”/>    <Prompt>      <Params>       <Param name=“BargeinType” value=“grammar”/>        <Paramname=“foo” value=“bar” />      <Params>    </Prompt>   </QA> </Style></speech:StyleSheet>

[1012] Command

[1013] Optional. The Command property of the Style object is used to setproperty values for all Command controls on a page that reference thisStyle.

[1014] CustomValidator

[1015] Optional. The CustomValidator property of the Style object isused to set property values for all CustomValidator controls on a pagethat reference this Style.

[1016] CompareValidator

[1017] Optional. The CompareValidator property of the Style object isused to set property values for all CompareValidator controls on a pagethat reference this Style.

[1018] SemanticItem

[1019] Optional. The SemanticItem property of the Style object is usedto set property values for all SemanticItem controls on a page thereference this Style.

[1020] The following properties may be set using the Style object.

[1021] QA Properties

[1022] AllowCommands

[1023] PlayOnce

[1024] XpathAcceptConfirms

[1025] XpathDenyConfirms

[1026] AcceptRejectThreshold

[1027] DenyRejectThreshold

[1028] FirstInitialTimeout

[1029] ConfirmByOmission

[1030] ConfirmIfEqual

[1031] OnClientActive

[1032] OnClientListening

[1033] OnClientComplete.

[1034] Prompt Properties

[1035] These apply to Prompts in QA, CompareValidator, CustomValidatorand Command controls.

[1036] Bargein

[1037] OnClientBookmark

[1038] OnClientError

[1039] Prefetch

[1040] Type

[1041] Lang

[1042] Params

[1043] Reco Properties

[1044] StartEvent

[1045] StopEvent

[1046] Mode

[1047] InitialTimeout

[1048] BabbleTimeout

[1049] MaxTimeout

[1050] EndSilence

[1051] Reject

[1052] OnClientSpeechDetected

[1053] OnClientSilence

[1054] OnClientNoReco

[1055] OnClientError

[1056] Lang

[1057] Params

[1058] Grammar Properties

[1059] These apply to both Reco and Dtmf grammars.

[1060] Type

[1061] Lang

[1062] Dtmf Properties

[1063] InitialTimeout

[1064] InterDigitTimeout

[1065] OnClientSilence

[1066] OnClientKeyPress

[1067] OnClientError

[1068] Params

[1069] Answer Properties

[1070] These apply to the Answers, ExtraAnswers and Confirmscollections.

[1071] ConfirmThreshold

[1072] Reject

[1073] Command Properties

[1074] Scope

[1075] AcceptCommandThreshold

[1076] CompareValidator Properties

[1077] ValidationEvent

[1078] Operator

[1079] Type

[1080] InvalidateBoth

[1081] CustomValidator Properties

[1082] ValidationEvent

[1083] SemanticItem Properties

[1084] BindOnChange

[1085] 8 QA Control

[1086] The QA control is responsible for querying the user with aprompt, starting a corresponding recognition object and processingrecognition results.

[1087] The QA control is rendered for both multimodal and voice-onlymodes. class QA : IndexedStyleReferenceSpeechControl { string id{get;set;}; int SpeechIndex{get; set;}; string ClientActivationFunction{get;set;}; string OnClientActive{get; set;}; string OnClientComplete{get;set;}; string OnClientListening{get; set;}; bool AllowCommands{get;set;}; bool PlayOnce{get; set;}; string XpathAcceptConfirms{get; set;};string XpathDenyConfirms{get; set;}; float AcceptRejectThreshold{get;set;}; float DenyRejectThreshold{get; set;}; floatFirstInitialTimeout{get; set;}; string StyleReference{get; set;}; boolConfirmByOmission{get; set;}; bool ConfirmIfEqual{get; set;};AnswerCollection Answers{get;}; AnswerCollection ExtraAnswers{get;};AnswerCollection Confirms{get;}; Prompt Prompt{get;}; Reco Reco{get;};Dtmf Dtmf{get;}; }.

[1088] 8.1 QA Properties

[1089] All properties of the QA control are available to the applicationdeveloper at design time.

[1090] SpeechIndex

[1091] Optional. Default is Zero, which is equivalent to no SpeechIndex.Only used in voice-only mode. Specifies the activation order of speechcontrols on a page and the activation order of composite controls. Allcontrols with SpeechIndex>0 will be run and then controls withSpeechIndex=0 will be run in source order. If more than one control hasthe same SpeechIndex, they are activated in source order. In situationswhere some controls specify SpeechIndex and some controls do not, thosewith SpeechIndex specified will be activated first, then the rest insource order. SpeechIndex values start at 1. An exception will be thrownfor non-valid values of SpeechIndex.

[1092] ClientActivationFunction

[1093] Optional. Only used in voice-only mode. Specifies a client-sidescript function which returns a Boolean value to determine when a QAcontrol is considered available for selection by the run-time controlselection algorithm. If not specified, it defaults to true (control isactive). The signature for ClientActivationFunction is as follows:

[1094] bool ClientActivationFunction (object lastActiveObj, stringlastCommandorException, int count)

[1095] where:

[1096] lastActiveObj is the last active control, e.g. QA,CustomValidator or CompareValidator. For the first activated QA on apage, lastActiveObj will be null.

[1097] lastCommandOrException is a Command type (e.g., “Help”) or a Recoevent (e.g., “Silence” or “NoReco”) of the last active control. For thefirst activated QA on a page or if the last active control is avalidator, lastCommandOrException will be an empty string.

[1098] count number of times the last active QA has been activatedconsecutively, 1 if this is the first acvtive QA on the page. Countstarts at 1 and has no limit. However, for the first activated QA on apage, count will be set to zero.

[1099] OnClientActive

[1100] Optional. Used in both multimodal and voice-only modes. Specifiesa client-side script that will be called after RunSpeech determines thisQA is active (voice-only mode) or after the startEvent is fired (inmultimodal) and before processing the QA (e.g., playing a prompt orstarting recognition). The onClientActive function does not returnvalues. The signature for onClientActive is as follows:

[1101] function onClientActive(string eventsource, stringlastCommandOrException, int Count, object SemanticItemList)

[1102] where:

[1103] eventsource is the id of the object (specified byReco.StartEvent) whose event started the Reco associated with the QA(for multimodal). eventsource will be null in voice-only mode.

[1104] lastCommandOrException is a Command type (e.g., “Help”) or a Recoevent (e.g., “Silence” or “NoReco”) for voice-only mode.lastCommandOrException is the empty string for multimodal.

[1105] Count is the number of times the QA has been activatedconsecutively. Count starts at 1 and has no limit for voice-only mode.Count is zero for multimodal.

[1106] SemanticItemList For voice-only mode, SemanticItemList is anassociative array that maps semantic item id to semantic item objects.For multimodal, SemanticItemList will be null.

[1107] OnClientComplete

[1108] Optional. Used in both multimodal and voice-only modes. Specifiesa client-side script that will be called after execution of a QA(successfully or not) and before passing dialog control back to theRunSpeech algorithm (in voice-only) or the end user (in multimodal). TheOnClientComplete function is called before postbacks to the server forQAs whose AutoPostBack attribute of the Answer object is set to true.The onClientComplete function does not return values. The signature foronClientComplete is as follows:

[1109] function onClientComplete (string eventsource, stringlastCommandOrException, int Count, object SemanticItemList)

[1110] where:

[1111] eventsource is the id of the object (specified by Reco.StopEvent)whose event stopped the Reco associated with the QA (for multimodal).eventsource will be null in voice-only mode.

[1112] lastCommandOrException is a Command type (e.g., “Help”) or a Recoevent (e.g., “Silence” or “NoReco”) for voice-only mode.lastCommandOrException is the empty string for multimodal.

[1113] Count is the number of times the QA has been activatedconsecutively. Count starts at 1 and has no limit for voice-only mode.Count is zero for multimodal.

[1114] SemanticItemList For voice-only mode, SemanticItemList is anassociative array that maps semantic item id to semantic item objects.For multimodal, SemanticItemList will be null.

[1115] OnClientListening

[1116] Optional. Used in both multimodal and voice-only modes. Specifiesa client-side script (function) that will be called/executed aftersuccessful start of the reco object. The main use is so the GUI canchange to show the user that they can start speaking. The function doesnot return any values. The signature for OnClientListening is asfollows:

[1117] function onClientListening(string eventsource, stringlastCommandOrException, int Count, object SemanticItemList)

[1118] where:

[1119] eventsource is the id of the object (specified byReco.StartEvent) whose event started the Reco associated with the QA(for multimodal). eventsource will be null in voice-only mode.

[1120] lastCommandOrException is a Command type (e.g., “Help”) or a Recoevent (e.g., “Silence” or “NoReco”) for voice-only mode.lastCommandOrException is the empty string for multimodal.

[1121] Count is the number of times the QA has been activatedconsecutively. Count starts at 1 and has no limit for voice-only mode.Count is zero for multimodal.

[1122] SemanticItemList For voice-only mode, SemanticItemList is anassociative array that maps semantic item id to semantic item objects.For multimodal, SemanticItemList will be null.

[1123] Note: In multimodal mode OnClientListening is only available ifauthor chooses to use StartEvent. If author decides to start recoprogrammatically, then onClientListening is not called for the authorbecause the author can detect when reco.start returns successfully.

[1124] Note: OnClientListening is ignored when specified in QA's that donot contain reco objects.

[1125] AllowCommands

[1126] Optional. Only used in voice-only mode. Indicates whether or notCommands may be activated for a QA control. When AllowCommands is set tofalse, no commands may be activated. Defaults to true.

[1127] PlayOnce

[1128] Optional. Only used in voice-only mode. Specifies whether or nota QA may be activated more than once per page. If not specified,PlayOnce is set to false. PlayOnce=“true” may be used to authorstatements like welcoming prompts. When a QA is reduced to a statement(no reco), setting PlayOnce=“false” will provide dialog authors with thecapability to enable a “repeat” functionality on a page that reads emailmessages.

[1129] XpathAcceptConfirms

[1130] Optional. Only used in voice-only mode. Specifies the path in thesml document (recognition result) that indicates the confirm items wereaccepted. Required if Confirms are specified. If XpathAcceptConfirms isspecified without a Confirm being specified it is ignored.XpathAcceptConfirms must be a valid xml path. An invalid xml path willcause a redirection to the default error page during run time.

[1131] XpathDenyConfirms

[1132] Optional. Used only in voice-only mode. Specifies the path in thesml document that indicates the confirm items were denied. Required ifConfirms are specified. If a Confirm is specified and XpathDenyConfirmsis not set an exception is thrown. If XpathDenyConfirms is specifiedwithout a Confirm being specified it is ignored. XpathDenyConfirms mustbe a valid xml path. An invalid xml path will cause a redirection to thedefault error page during run time.

[1133] AcceptRejectThreshold

[1134] Optional. Used only in voice-only mode. If confidence for anaccept confirm is not above this threshold no action will be taken.Legal values are 0-1 and are platform specific. An exception will bethrown for out of range AcceptRejectThreshold values. Default is zero

[1135] DenyRejectThreshold

[1136] Optional. Used only in voice-only mode. If confidence for a denyconfirm is not above this threshold no action will be taken. Legalvalues are 0-1 and are platform specific. An exception will be thrownfor out of range DenyRejectThreshold values. Default is zero.

[1137] FirstInitialTimeout

[1138] Optional. Only used in voice-only mode. Specifies the initialtimeout in msec for the QA when count==1. The status of theTargetElements specified in the Confirms answer list will be set to“Confirmed” if no speech is detected within firstInitialTimeoutmilliseconds. If not specified the default value of firstInitialTimeoutis 0, which means that silence does not imply confirmation of theAnswer. An exception will be thrown if firstInitialTimeout is specifiedfor a QA that does not contain Confirms. An exception will be thrown fornegative values of FirstInitialTimeout.

[1139] StyleReference

[1140] Optional. Used in both multimodal and voice-only modes. Specifiesthe name of a Style object. At render time, the QA control will searchfor the named Style control and will use any property values specifiedon the Style as default values for its own properties. Explicitly setproperty values on the control will override those set on the Style.

[1141] ConfirmByOmission

[1142] Optional. Used only in voice-only mode. Default is true. Thisflag controls confirmation of more than one item. If the flag is set totrue, then any semantic items whose xpath is not present in the recoresult, will be set to Confirmed. ConfirmByOmission enables thefollowing scenario:

[1143] (ConfirmByOmission=true)

[1144] Q: Flying from?

[1145] A: Boston.

[1146] Q: Flying to?

[1147] A: Seattle.

[1148] Q: From Boston to Seattle?

[1149] A: From NY.

[1150] (Seattle is confirmed as destination city).

[1151] ConfirmIfEqual

[1152] Optional. Used only in voice-only mode. Default is true. Thisflag controls the processing of corrections during confirmation. IfConfirmIfEqual is true and a recognized correction is the same valuealready in the semantic item, the item is maked confirmed. IfConfirmIfEqual is false and a recognized correction is the same valuealready in the semantic item, the item is maked as needing confirmation.

[1153] Answers

[1154] Optional. An array of answer objects. This list of objects isused both to determine activation, and to carry out semantic processinglogic. An exception will be thrown if an Answers collection containsnon-answer objects.

[1155] ExtraAnswers

[1156] Optional. An array of answer objects. These items are not usedfor activation, but they are taken into account when processingrecognition results. If an ExtraAnswer is recognized, it will overwritethe semantic item it points to, even if it was previously confirmed.

[1157] Confirms

[1158] Optional. An array of answer objects. These items are used foractivation if the answers array is empty and they affect theconfirmation logic.

[1159] Prompt

[1160] Optional for multimodal. Required for voice-only. An exception isthrown if a Prompt is not specified in voice-only mode.

[1161] Reco

[1162] Optional for multimodal and voice-only. Typically, only one recocan be specified in a QA.

[1163] Dtmf

[1164] Optional. Only used in voice-only mode. Typically, only one Dtmfcan be specified in a QA.

[1165] 9 Command Control

[1166] The Command control provides a way for obtaining user input thatis not an answer to the question at hand (eg, Help, Repeat, Cancel), andwhich does not map to textual input into primary controls. A Commandspecifies an activation scope, which means that its grammar is active(in parallel with the current recognition grammar) for every QA withinthat scope. Commands have a type attribute which is used to implement achain of events: Commands of the same type at QAs lower in scope canoverride superior commands with context-sensitive behavior (and evendifferent/extended grammars if necessary) and to notify the QA whatcommand was uttered (via the reason parameter)

[1167] Commands are not rendered for multimodal mode. class Command :SpeechControl { string id{get; set;}; string Scope{get; set;}; stringType{get; set;}; string XpathTrigger{get; set;}; floatAcceptCommandThreshold{get; set;}; string OnClientCommand{get; set;};bool AutoPostBack{get; set;}; TriggeredEventHandler OnTriggered; stringStyleReference{get; set;}; Prompt Prompt{get;}; Grammar Grammar{get;};Grammar DtmfGrammar{get;}; }

[1168] 9.1 Conmand Properties

[1169] All properties of the Command control are available to theapplication developer at design time.

[1170] Scope

[1171] Required. Only used in voice-only mode. Specifies the id of a QAor other ASP.NET control (e.g., form, panel, or table). Scope is used inCommands to specify when the Command's grammars will be active.Exceptions are thrown if Scope is invalid or not specified.

[1172] Type

[1173] Required. Only used in voice-only mode. Specifies the type ofcommand (eg ‘help’, ‘cancel’ etc.) in order to allow the overriding ofidentically typed commands at lower levels of the scope tree. Any stringvalue is possible in this attribute, so it is up to the author to ensurethat types are used correctly. An exception is thrown if Type is notspecified.

[1174] Note: An exception will be thrown if more than 1 Command of sameType has the same Scope. For example, 2 Type-“Help” Commands for thesame QA (Scope=“QA1”).

[1175] AcceptCommandThreshold

[1176] Optional. Only used in voice-only mode. Specifies the minimumconfidence level of recognition that is necessary to trigger the command(this is likely to be used when higher than usual confidence isrequired, e.g. before executing the result of a ‘Cancel’ command). Legalvalues are 0-1. Default value is 0. Exceptions will be thrown for out ofrange AcceptCommandThreshold values.

[1177] If a command is matched (its xpathTrigger is present in therecoResult) no further commands will be processed, and no Answers,ExtraAnswers, Confirms, etc. will be processed. Then, if the confidenceof the node specified by XpathTrigger is greater than or equal to theacceptThreshold, the active QAs LastCommandOrException is set to theCommand's type, and the Command's onCommand function is called.Otherwise (if the confidence of the node is less than theacceptThreshold) the active QAs LastCommandOrException is set to“NoReco” and the active QAs Reco's OnClientNoReco function is called.

[1178] XpathTrigger

[1179] Required. Only used in voice-only mode. SML document path thattriggers this command. An exception will be thrown if XpathTrigger isnot specified. XpathTrigger must be a valid xml path. An invalid xmlpath will cause a redirection to the default error page during run time.

[1180] OnClientCommand

[1181] Optional. Only used voice-only mode. Specifies the client-sidescript function to execute on recognition of the Command's grammar. Thefunction does not return any values. The signature for OnClientCommandis as follows:

[1182] function OnClientCommand(XMLNode smlNode)

[1183] where: smlNode is the matched SML node.

[1184] Note: If AutoPostBack is set to true, the OnClientCommandfunction is executed before posting back to the server. If the authorwishes to persist any page state across postback, the OnClientCommandfunction is a good place to invoke the ClientViewState object ofRunSpeech.

[1185] AutoPostBack

[1186] Optional. Only used in voice-only mode. Specifies whether or notthe Command control posts back to the server each time a Command grammaris recognized. Default is false. If set to true, the server-sideTriggered event is fired.

[1187] The internal state of the voice-only page is maintainedautomatically during postback. Authors may use the ClientViewStateobject of RunSpeech to declare and set additional values they wish topersist across postbacks.

[1188] OnTriggered

[1189] Optional. Only used in voice-only mode. Specifies a server-sidescript function to be executed when the Triggered event is fired (seeautopostback attribute above). This handler must have the form (inC#—the signature would look slightly different in other languages):

[1190] void myFunction (object sender, CommandTriggeredEventArgs e);

[1191] The handler can be assigned to in two differentways—declaratively: <speech:Command ... OnTriggered=“myFunction” .../>or programmatically: Command.Triggered += new TriggeredEventHandler(myFunction );

[1192] TriggeredEventHandler is what is called a “delegate”—it basicallyspecifies the signature of functions which can handle its associatedevent type. It looks like this:

[1193] public delegate void TriggeredEventHandler(object sender,TriggeredEventArgs e);

[1194] where:

[1195] TriggeredEventArgs is a class derived from System.EventArgs whichcontains one public property, string Value.

[1196] An exception will be thrown if AutoPostBack is set to true and nohandler is specified for the Triggered event. An exception will bethrown if AutoPostBack is set to false and a handler is specified forthe Triggered event.

[1197] StyleReference

[1198] Optional. Only used in voice-only mode. Specifies the name of aStyle object. At render time, the QA control will search for the namedStyle control and will use any property values specified on the Style asdefault values for its own properties. Explicitly set property values onthe control will override those set on the Style.

[1199] Prompt

[1200] Optional. May be used to specify prompt to be played for globalcommands.

[1201] Granmar

[1202] Optional. The grammar object which will listen for the command.

[1203] Note: The grammar object is optional because the QA scoped bythis command may contain the rule that generates this command's Xpath.The author has the flexibility of specifying the rule in the QA controlor the Command control.

[1204] DtmfGrammar

[1205] Optional. The DtmfGrammar object which will activate the command.Available at run time.

[1206] Note: The DtmfGrammar object is optional because the QA scoped bythis command may contain the rule that generates this command's Xpath.The author has the flexibility of specifying the rule in the QA controlor the Command control. DtmfGrammars for all Commands along the QA'sscope chain will be combined into the Grammars collection for the QA'sDtmf object.

[1207] Speech Controls does not provide a set of common commands—e.g.,help, cancel, repeat.

[1208] 10 CompareValidator Control

[1209] This control compares two values, applying the operator, and ifthe comparison is false, invalidates the item specified bySemanticItemToValidate. Optionally, both items (ToCompare andToValidate) are invalidated. The CompareValidator is triggered on theclient by change or confirm events; however, validation prompts areplayed in SpeechIndex order.

[1210] The CompareValidator control is rendered for voice-only mode. Formultimodal, ASP.NET validator controls may be used. classCompareValidator : IndexedStyleReferenceSpeechControl { string id{get;set;}; int SpeechIndex{get; set;}; ValidationType Type{get; set;};string ValidationEvent{get; set;}; string SemanticItemToCompare{get;set;}; string ValueToCompare{get; set;}; stringSemanticItemToValidate{get; set;}; ValidationCompareOperatorOperator{get; set;}; bool InvalidateBoth{get; set;}; stringStyleReference{get; set;}; Prompt Prompt{get;}; }

[1211] 10.1 CompareValidator Properties

[1212] All properties of the CompareValidator control are only used invoice-only mode and are available to the application developer at designtime.

[1213] SpeechIndex

[1214] Optional. Specifies the activation order of CompareValidatorcontrols on a page. If more than one control has the same SpeechIndex,they are activated in source order. In situations where some controlsspecify SpeechIndex and some controls do not, those with SpeechIndexspecified will be activated first, then the rest in source order.SpeechIndex values start at 1. An exception will be thrown for non-validvalues of SpeechIndex.

[1215] Type

[1216] Required. Sets the datatype of the comparison. Legal values are“String”, “Integer”, “Double”, “Date”, and “Currency”. Default value is“String”.

[1217] ValidationEvent

[1218] Default is “onconfirmed”. ValidationEvent may be set to one oftwo values, either “onchange” or “onconfirmed”.

[1219] If ValidationEvent is set to “onchanged”, the CompareValidatorwill be run each time the value of the Text property of the associatedSemanticItem changes. The CompareValidator control will be run beforethe SemanticItem's OnChanged handler is called. The SemanticItem'sOnChanged handler will only be called if the CompareValidator doesindeed validate the changed data. If the CompareValidator invalidatesthe data, the State of the SemanticItem is set to Empty and theOnChanged handler is not called.

[1220] If ValidationEvent is set to “onconfirmed”, the CompareValidatorwill be run each time the State of the associated SemanticItem changesto Confirmed. The CompareValidator control will be run before theSemanticItem's OnConfimed handler is called. The SemanticItem'sOnConfirmed handler will only be called if the CompareValidator doesindeed validate the changed data. If the CompareValidator invalidatesthe data, the State of the SemanticItem is set to Empty and theOnConfirmed handler is not called.

[1221] After processing all SemanticItems involved a recognition turn,RunSpeech starts again. At that point, the previously failed validatorswill be active and RunSpeech will select the first QA/Validator that isactive in SpeechIndex order. It is the author's responsibility to placethe validator controls directly before the QA control that collects theanswer for the SemanticItem in order to get the correct behavior.

[1222] SemanticItemToCompare

[1223] Optional. Either SemanticItemToCompare or ValueToCompare must bespecified. Specifies the Id of the SemanticItem which will be used. asthe basis for the comparison. Available at design time and run time. Anexception will be thrown if either SemanticItemToCompare orValueToCompare is not specified.

[1224] ValueToCompare

[1225] Optional. Either SemanticItemToCompare or ValueToCompare must bespecified. Specifies the value to be used as the basis for thecomparison. The author may wish to specify the value here instead oftaking the value from the semantic item. If both ValueToCompare andSemanticItemToCompare are set, SemanticItemToCompare takes precedence.An exception will be thrown if either SemanticItemToCompare orValueToCompare is not specified. An exception will be thrown ifValueToCompare can not be converted to a valid Type.

[1226] SemanticItemToValidate

[1227] Required. Specifies the Id of the SemanticItem that is beingvalidated against either ValueToCompare or SemanticItemToCompare. Anexception will be thrown for unspecified SemanticItemToValidate.

[1228] Operator

[1229] Optional. One of “Equal”, “NotEqual”, “GreaterThan”,“GreaterThanEqual”, “LesserThan”, “LesserThanEqual”, “DataTypeCheck”.Default value is “Equal”. The values are compared in the followingorder: Value to Validate [operator] ValueToCompare.

[1230] InvalidateBoth

[1231] Optional. If true, both SemanticItemToCompare andSemanticItemToValidate are marked Empty. Default is false (i.e.,invalidate only the SemanticItemtToInvalidate). IfSemanticItemToValidate has not been set (i.e. ValueToCompare has beenspecified), InvalidateBoth is ignored.

[1232] The following example illustrates the usage of the InvalidateBothattribute. The scenario is an itinerary application. The user hasalready been prompted and answered the question for departing city. Atthis point in the dialog an ASP.NET textbox control has been filled withthe recognition results (assume txtDepartureCity.Value=“Austin”).

[1233] The next QA prompts the user for the arrival city, theSemanticItem object binds to txtArrivalCity.Value.

[1234] In response to the prompt, the user says “Boston”. However, therecognition engine returns “Austin” (e.g. arrival city is same asdeparting city).

[1235] The CompareValidator control may be used to direct the dialogflow in this case to re-prompt the user for both departing and arrivingcities: <CompareValidator id=“compareCities” SpeechIndex=“5”Type=“String”     SemanticItemToCompare=“si_DepartureCity”    SemanticItemToValidate=“si_ArrvivalCity”     Operator=“NotEqual”    InvalidateBoth=“True”     runat=“server” </CompareValidator>

[1236] StyleReference

[1237] Optional. Specifies the name of a Style object. At render time,the QA control will search for the named Style control and will use anyproperty values specified on the Style as default values for its ownproperties. Explicitly set property values on the CompareValidatorcontrol will override those set on the Style.

[1238] Prompt

[1239] Optional. Prompt to indicate the error.

[1240] 11 Customvalidator Control

[1241] The CustomValidator control is used to validate recognitionresults when complex validation algorithms are required. The controlallows dialog authors to specify their own validation routines. TheCustomValidator is triggered on the client by change or confirm events;however, validation prompts are played in SpeechIndex order.

[1242] The CustomValidator control is only rendered for voice-only mode.For multimodal, ASP.NET validator controls may be used. classCustomValidator : IndexedStyleReferenceSpeechControl { string id{get;set;}; int SpeechIndex{get; set;}; string ValidationEvent{get; set;};string SemanticItemToValidate{get; set;}; stringClientValidationFunction{get; set;}; string StyleReference{get; set;};Prompt Prompt{get;}; }

[1243] 11.1 CustomValidator Properties

[1244] All properties of the CustomValidator control are only used invoice-only mode and are available to the application developer at designtime.

[1245] SpeechIndex

[1246] Optional. Only used in voice-only mode. Specifies the activationorder of speech controls on a page and the activation order of compositecontrols. If more than one control has the same SpeechIndex, they areactivated in source order. In situations where some controls specifySpeechIndex and some controls do not, those with SpeechIndex specifiedwill be activated first, then the rest in source order. SpeechIndexvalues start at 1. An exception will be thrown for non-valid values ofSpeechIndex.

[1247] ValidationEvent

[1248] Default is “onconfirmed”. ValidationEvent may be set to one oftwo values; either “onchange” or “onconfirmed”.

[1249] If ValidationEvent is set to “onchanged”, the CustomValidatorwill be run each time the value of the Text property of the associatedSemanticItem changes. The CustomValidator control will be run before theSemanticItem's OnChanged handler is called. The SemanticItem's OnChangedhandler will only be called if the CustomValidator does indeed validatethe changed data. If the CustomValidator invalidates the data, the Stateof the SemanticItem is set to Empty and the OnChanged handler is notcalled.

[1250] If ValidationEvent is set to “onconfirmed”, the CustomValidatorwill be run each time the State of the associated SemanticItem changesto Confirmed. The CustomValidator control will be run before theSemanticItem's OnConfimed handler is called. The SemanticItem'sOnConfirmed handler will only be called if the CustomValidator doesindeed validate the changed data. If the CustomValidator invalidates thedata, the State of the SemanticItem is set to Empty and the OnConfirmedhandler is not called.

[1251] After processing all SemanticItems involved a recognition turn,RunSpeech starts again. At that point, the previously failed validatorswill be active and RunSpeech will select the first QA/Validator that isactive in SpeechIndex order. It is the author's responsibility to placethe validator controls directly before the QA control that collects theanswer for the SemanticItem in order to get the correct behavior.

[1252] SemanticltemToValidate

[1253] Required. Specifies the id of the SemanticItem that is beingvalidated. An exception will be thrown for unspecified SemanticItemToValidate.

[1254] ClientValidationFunction

[1255] Required. Specifies a function that checks the value of theSemanticItemToValidate.AttributeToValidate and returns true or falseindicating whether the value is valid or invalid. The signature forClientValidationFunction is as follows:

[1256] bool ClientValidationFunction (string value)

[1257] where:

[1258] value is the contents of

[1259] ElementToValidate.AttributeToValidate.

[1260] An exception will be thrown if ClientValidationFunction is notspecified

[1261] StyleReference

[1262] Optional. Specifies the name of a Style object. At render time,the QA control will search for the named Style control and will use anyproperty values specified on the Style as default values for its ownproperties. Explicitly set property values on the control will overridethose set on the Style.

[1263] Prompt

[1264] Optional. Prompt to indicate the error.

[1265] 12 Answer Object

[1266] The Answer object contains information on how to processrecognition results and bind the results to controls on an ASP.NET page.

[1267] How Answer object is used.

[1268] Voice-only mode.

[1269] The RunSpeech script uses the Answer object to perform answerprocessing on the client. Answer processing begins when the OnReco eventfired by the speech platform is received by the client. The resultantSML document returned by the speech platform is searched for the nodespecified by the required XpathTrigger attribute. If the XpathTriggernode is found in the SML document and contains a non-null value, thevalue is is filled into the semantic item specified in the SemanticItemproperty of the answer.

[1270] For non-existant XpathTrigger in the SML document or null valueof XpathTrigger, RunSpeech looks for the next QA to activate.

[1271] After the non-null value of the XpathTrigger node is found,RunSpeech invokes the ClientNormalization function (if specified). TheClientNormalizationFunction returns a text string that reflects theauthor-defined transformation of the value of the XpathTrigger node. Forexample, the author may wish to transform the date “Nov. 17, 2001”returned by the speech platform to “Nov. 17, 2001”. Semantic items areused for both simple and complex data binding.

[1272] The SML document returned by the speech platform maycontain aplatform-specific confidence rating for each XpathTrigger node. Duringanswer processing, RunSpeech compares this confidence rating to thevalue specified in the ConfirmThreshold attribute of the Answer object.Results of the comparison are then used to set the internal confirmedstate of the semantic item. This state information is subsequently usedto determine whether or not an answer requires confirmation from theuser.

[1273] RunSpeech internally marks an answer as needing confirmation ifthe confidence returned with the XpathTrigger is less than or equal tothe value of the ConfirmThreshold attribute. Otherwise RunSpeechinternally marks the semantic item associated with the answer asconfirmed. This internal state information is used during confirmationprocessing.

[1274] Multimodal.

[1275] The Answer object is used in multimodal scenarios by theMultimodal.js script just as it is used by RunSpeech in voice-only(described above) with one exception. In multimodal, platform-specificconfidence ratings are not compared to the ConfirmThreshold attribute ofthe Answer object, therefore internal state information of each answeris not maintained. Confirmation of results is done visually. If anincorrect result is bound to a visual control, the user senses theproblem visually and may then initiate another speech input action tocorrect the error. Rendered for both multimodal and voice-only modesclass Answer : Control { string id{get; set;}; float   Reject{get;set;}; float   ConfirmThreshold{get; set;}; string XpathTrigger{get;set;}; string SemanticItem{get; set;}; stringClientNormalizationFunction{get; set;}; string StyleReference{get;set;}; }

[1276] 12.1 Answer Properties

[1277] All properties of the Answer object are available to theapplication developer at design time.

[1278] Reject

[1279] Optional. Used in both multimodal and voice-only modes. Specifiesthe rejection threshold for the Answer. Answers having confidence valuesbelow Reject will cause a noReco event to be thrown. If not specified,the value 0 will be used. Legal values are 0-1 and are platformspecific. An exception will be thrown for out of range Reject values.

[1280] Rejected Answers are treated as if they were not present in thereco result to begin with. If, after this processing, no relevantinformation remains (no Answers, ExtraAnswers, Confirms, Commands, orxpathAcceptConfirms/xpathDenyConfirms), an onnoreco event is fired(which mimics exactly the tags version).

[1281] ConfirmThreshold

[1282] Optional. Used in voice-only mode. Specifies the minimumconfidence level of recognition that is necessary to mark this item asconfirmed. If the confidence of the matched item is less than or equalto this threshold, the item is marked as needing confirmation. Legalvalues are 0-1. Default value is 0. An exception will be thrown for outof range ConfirmThreshold values.

[1283] XpathTrigger

[1284] Required for Answers and ExtraAnswers. Optional for Confirms.Used in both multimodal and voice-only modes. Specifies what part of theSML document this answer refers to. It is specified as an XPath on theSML output from recognition. An exception will be thrown if XpathTriggeris not specified for Answers or ExtraAnswers. XpathTrigger must be avalid xml path. An invalid xml path will cause a redirection to thedefault error page during run time.

[1285] For Confirms, if XpathTrigger is not set or set to the emptystring, the confirm won't allow for correction. Yes/no confirmations areenabled when XpathTrigger is used in this way.

[1286] SemanticItem

[1287] Optional. Used in both multimodal and voice-only modes.

[1288] ClientNormalizationFunction

[1289] Optional. Used in both multimodal and voice-only modes. Specifiesa client-side function that will take the matched sml node as aparameter and returns a string that reflects author-specifiednormalization (transformation) of the recognized item. The signature forClientNormalizationFunction is as follows:

[1290] string ClientNormalizationFunction(XMLNode SMLnode, objectSemanticItem)

[1291] where:

[1292] SMLnode is the node specified in the Xpath.

[1293] SemanticItem is the client-side SemanticItem object specified inthe Answer object.

[1294] StyleReference

[1295] Optional. Used in both multimodal and voice-only modes. Specifiesthe name of a Style object. At render time, the Answer object willsearch for the named Style control and will use any property valuesspecified on the Style as default values for its own properties.Explicitly set property values by the Answer object will override thoseset on the referenced Style.

[1296] 13 SemanticMap Control

[1297] SemanticMap is a container of SemanticItem objects. classSemanticMap : SpeechControl {   SemanticItemCollection SemItems{get;};  SemanticItem GetSemanticItem (string name); }

[1298] 13.1 SemanticMap Properties

[1299] SemItems

[1300] A collection of SemanticItem objects.

[1301] 13.2 SemanticMap Methods

[1302] GetSemanticItem

[1303] This is a function that takes the id of a SemanticItem andreturns the SemanticItem object. The signature of GetSemanticItem is:

[1304] function GetSemanticItem(string id)

[1305] 14 SemanticItem Object

[1306] The SemanticItem object describes where and when an Answer'srecognition results are written to visual controls on a page. The objectalso keeps track of the current state of Answers, i.e., whether anAnswer has changed or been confirmed. class SemanticItem : Control {  string id{get; set;};   string TargetElement{get; set;};   stringTargetAttribute{get; set;};   bool BindOnChanged{get; set;};   stringBindAt{get; set;};   bool AutoPostBack{get; set;};   stringOnClientChanged{get; set;};   string OnClientConfirmed{get; set;};  SemanticEventHandler  Changed;   SemanticEventHandler  Confirmed;  string Text{get;};   SemanticState State{get;};   StringDictionaryAttributes{get; set;};   string StyleReference{get;}; }

[1307] 14.1 SemanticItem Properties

[1308] id

[1309] Required. The programmatic id of this semantic item.

[1310] TargetElement

[1311] Optional. Used in both multimodal and voice-only modes. Specifiesthe id of the visual control to which the recognition results should bewritten. If specified, default binding will occur when the value ischanged or confirmed depending on the value of BindOnChanged. Anexception is thrown if TargetElement is the id of multiple controls.

[1312] TargetAttribute

[1313] Optional. Used in both mutimodal and voice-only modes. Specifiesthe property name of the TargetElement to which this answer should bewritten. The default value is null. An exception will be thrown ifTargetElement is specified and TargetAttribute is not specified.

[1314] BindOnChanged

[1315] Optional. Used voice-only mode, ignored in multimodal. Default isfalse. In VoiceOnly mode, BindOnChanged controls when to bindrecognition results to visual elements.

[1316] A value of true causes binding everytime the value of theSemanticItem changes.

[1317] A value of false causes binding only when the SemanticItem hasbeen confirmed.

[1318] BindAt

[1319] Optional. Used in both mutimodal and voice-only modes. Can beomitted or set to “server”. Default is null (omitted). If BindAt is setto “server”, it indicates that the TargetElement/TargetAttribute pairrefers to a server-side control or property. An exception will be thrownwhen BindAt is set to an invalid value.

[1320] If BindAt is “server”, an exception will be thrown if:

[1321] SemanticItem.TargetElement is not a server-side control, or

[1322] SemanticItem.TargetAttribute is not a member of the controlspecified by SemanticItem.TargetElement, or

[1323] SemanticItem.TargetAttribute is a member ofSemanticItem.TargetElement, but is not of type string, or

[1324] SemanticItem.TargetAttribute is a string, but is read-only.

[1325] AutoPostBack

[1326] Optional. Used in both multimodal and voice-only modes. Specifieswhether or not the control posts back to the server when the bindingevent is fired. The binding event can be onChanged or onConfirmed and iscontrolled by the value of BindonChange. Default is false.

[1327] The state of the voice-only page is maintained automaticallyduring postback. Authors may use the ClientViewState object of RunSpeechto declare and set any additional values they wish to persist acrosspostbacks.

[1328] OnClientChanged

[1329] Optional. Used in both multimodal and voice-only modes. Specifiesa client-side function to be called when the value of the Text propertyof this SemanticItem changes. The function does not return any values.The signature for OnClientChanged is as follows:

[1330] function OnClientChanged(object SemanticItem)

[1331] where SemanticItem is the client-side SemanticItem object.

[1332] Note: If AutoPostBack is set to true, the OnClientChangedfunction is executed before posting back to the server. If the authorwishes to persist any page state across postback, the OnClientChangedfunction is a good place to access the ClientViewState object ofRunSpeech.

[1333] OnClientConfirmed

[1334] Optional. Used in both multimodal and voice-only modes.

[1335] Specifies a client-side function to be called when thisSemanticItem's [value is confirmed. The function does not return anyvalues. The signature for OnClientConfirmed is as follows:

[1336] function OnClientConfirmed(object SemanticItem)

[1337] where SemanticItem is the client-side SemanticItem object.

[1338] Note: If AutoPostBack is set to true, the OnClientConfirmedfunction is executed before posting back to the server. If the authorwishes to persist any page state across postback, the OnClientConfirmedfunction is a good place to access the ClientViewState object ofRunSpeech

[1339] Changed

[1340] Optional. Used in both multimodal and voice-only modes. Specifiesa server-side script function to be executed when the Changed event isfired.

[1341] The signature of a SemanticEventHandler is: (in C#—the signaturewould look slightly different in other languages)

[1342] public delegate void SemanticEventHandler (object sender,SemanticEventArgs e

[1343] where:

[1344] SemanticEventArgs is a class derived from System.EventArgs.public class SemanticEventArgs : EventArgs {   public string  Text{get;};   public StringDictionary Attributes {get;} }

[1345] Text

[1346] Returns the value that this SemanticItem has been set to.

[1347] State

[1348] Returns the state of this SemanticItem.

[1349] Confirmed

[1350] Optional. Used in both multimodal and voice-only modes. Specifiesa server-side script function to be executed when the Confirmed event isfired. In multimodal mode, the Confirmed event will be fired immediatelyafter the Changed event.

[1351] The signature of a SemanticEventHandler is: (in C#—the signaturewould look slightly different in other languages)

[1352] public delegate void SemanticEventHandler (object sender,SemanticEventArgs e);

[1353] where:

[1354] SemanticEventArgs is a class derived from System.EventArgs.public class SemanticEventArgs : EventArgs {   public string Text {get;}  public StringDictionary Attributes {get;} }

[1355] Text

[1356] Read only. Returns the value that this SemanticItem has been setto.

[1357] State

[1358] Read only. Returns the state of this SemanticItem.

[1359] Text

[1360] The text value that this SemanticItem has been set to. Default isnull.

[1361] State

[1362] The confirmation state of this SemanticItem. Values of State willbe one of SemanticState.Empty, SemanticState.NeedsConfirmation orSemanticState.Confirmed.

[1363] Attributes

[1364] Optional. Used in both multimodal and voice-only modes. This is acollection of name/value pairs. Attributes is used to pass user definedinformation to the client-side semantic item and back to the server(they are kept synchronized). Attributes may only be setprogrammatically. For example:

[1365] SemanticItem.Attributes[“myvarname”]=“myvarvalue”

[1366] Attributes are not cleared when the SemanticItem is reset by thesystem. If developers wish to reset the attributes, they must do somanually.

[1367] StyleReference

[1368] Optional. Used in both multimodal and voice-only modes. Specifiesthe name of a Style object. At render time, the QA SemanticItem objectwill search for the named Style control and will use any property valuesspecified on the style as default values for its own properties.Explicitly set property values by the SemanticItem object will overridethose set on the referenced Style.

[1369] 14.2 SemanticItem Client-Side Object //Notation doesn't implyprogramming language class SemanticItem {   SemanticItem (sco, id,targetElement, targetAttribute,     bindOnChanged, bindAtServer,autoPostback,     onClientChanged, onClientConfirmed,   hiddenFieldID,    value, state);   SetText (string text, boolean isConfirmed);  Confirm( );   Clear( );   Empty( );   AddValidator (validator);  IsEmpty( );   NeedsConfirmation( );   IsConfirmed( );   Encode( );  Object value; //Read only   string state; //Read only   objectattributes; }

[1370] SetText (String Text, Boolean isConfirmed)

[1371] The SetText method of the client side semantic item object isused to alter the value property. The partmeters are

[1372] string text the string which will become the value of the theSemantic Item

[1373] Boolean isConfirmed determines whether the Semantic Item stateproperty is “confirmed” (if true) or “needs confirmation” if false

[1374] Confirm( )

[1375] This method sets the state property of the Semantic Item propertyto “confirmed.”

[1376] Clear( )

[1377] This method sets the value property of the Semantic Item to NULLand sets the state property to “empty.”

[1378] Empty( )

[1379] AddValidator (validator)

[1380] IsEmpty( )

[1381] This method checks to see if the state property of the SemanticItem and returns true if it is “empty” and false if it is “needsconfirmation” or “confirmed.”

[1382] NeedsConfirmation( )

[1383] This method checks to see if the state property of the SemanticItem and returns true if it is “needs confirmation” and false if it is“empty” or “confirmed.”

[1384] IsConfirmed( )

[1385] This method checks to see the state property of the Semantic Itemand returns true if it is “confirmed” and false if it is “needsconfirmation” or “empty.”

[1386] Encode( )

[1387] Object Value

[1388] ReadOnly.

[1389] String State

[1390] Read Only.

[1391] Object Attributes

[1392] 14.3 Run-Time Behavior

[1393] As a general rule, the order of execution for every transitionEmpty->NeedsConfirmation or NeedsConfirmation->Confirmed:

[1394] Client-side binding (if needed)

[1395] Client-side event

[1396] If (Autopostback), trigger submit.

[1397] On the server, the order of execution is:

[1398] Server-side binding (if needed)

[1399] Server-side event.

[1400] If the semantic item is programmatically changed in the server,no events (server or client side) will be thrown.

[1401] If (BindonChanged=false) and (Autopostback=true) and we have bothChanged and Confirmed handlers, both events will be triggered, in order.

[1402] Changed events will be thrown in the server (if needed andhandlers are set) even if the server-side value is the same as theprevious one (didn't change apparently).

[1403] If AutoPostBack is set to true, the controls will cause twopostbacks, synchronized with onChanged, and onConfirmed.

[1404] 15 Prompt Object

[1405] The prompt object contains information on how to play prompts.All the properties defined are read/write properties.

[1406] Rendered for voice-only. Not rendered for multimodal.

[1407] How Prompt Object is Used

[1408] Voice-Only

[1409] The Prompt object is a required element of the QAcontrol-RunSpeech uses the Prompt object to select the appropriate textfor the prompt and then play the prompt on the client.

[1410] After RunSpeech determines which QA to activate it eitherincrements or initializes the count attribute of the QA. The countattribute is incremented if the QA being activated was the same QA thatwas active during the last loop through RunSpeech. The count attributeis initialized to count=1 if this is the first time the QA has beenactivated. The QA's count attribute may be used by the script specifiedin the PromptSelectFunction attribute of the Prompt object.

[1411] RunSpeech then sets out to determine which text will besynthesized and played back to the user. The dialog author has theoption of providing a script function for prompt text that is complex tobuild, or simply specifying the prompt text as content of the Promptobject. If RunSpeech detects the existence of an author-specifiedPromptSelectFunction, it passes the text returned from thePromptSelectFunction to the speech platform for synthesis and playbackto the user. Otherwise RunSpeech will pass the text in the content ofthe Prompt object to the speech platform.

[1412] If a serious or fatal error occurs during the synthesis process,the speech platform will fire the onError event. RunSpeech receives thisevent, sets lastCommandOrException to “PromptError” and calls the scriptfunction specified by the OnClientError attribute. The dialog author maythen choose to take appropriate action based upon the type of error thatoccurred.

[1413] After the prompt playback has finished, the speech platform firesthe oncomplete event which is caught by RunSpeech. RunSpeech then looksfor the Reco object associated with the current QA. If a Reco object isfound (i.e., the QA is not just a prompting mechanism), RunSpeechrequests the speech platform to start the recognition process.

[1414] Finally, RunSpeech examines the value of the PlayOnce attributeof the QA containing the Prompt object. If PlayOnce is true, RunSpeechdisables the Prompt object for subsequent activations of this same QA.

[1415] If speech is detected during the playing of the prompt, theplayback of the prompt will be stopped automatically by the platform.RunSpeech catches the onbargein event and halts execution. Since aprompt.OnComplete event may not follow a bargein, RunSpeech resumes whena listen event is received.

[1416] If a bookmark is encountered, Runspeech activates the functionspecified by the OnClientBookmark property.

[1417] Multimodal.

[1418] The Prompt object is not used in multimodal scenarios.

[1419] PromptSelectFunction

[1420] The following three examples illustrate using thePromptSelectionFunction to select or modify prompt text using theparameters available to PromptSelectFunction.

[1421] The first example shows how to use the count parameter to selecta prompt based upon the number of times the QA has been activated. Thescenario is:

[1422] A user calls a menu based service, enters password. Server-sideprocessing determines the user's first and last name and inserts thename information into hidden textboxes (txtFirstName.value andtxtLastName.value) on the welcome page. The welcome page contains a QAwhich prompts the user to enter the desired service. The QA's Promptobject is built to handle 1) the prompt to play for a first time passand 2) the prompt to play if the user fails to select a service at thefirst prompting (i.e., the same QA is activated after a timeoutexpires). <speech:QA id=“welcomeQA” runat=“server”>   <Promptid=“welcomePrompt”       PromptSelectFunction=“SelectWelcomePrompt” />  <Reco id=“welcomeReco” mode=“automatic”>     <Grammars>      <speech:grammar id=“welcomeGrammar”        src=“http://mysite/services.xml” runat=“server” />    </Grammars>   </Reco>   <Answers>     <speech:answerid=“servicesAnswer” SemanticItem =        “siService” runat=“server” />  </Answers> </speech:QA> <script> functionSelectWelcomePrompt(lastCommandOrException, count, assocArray) {  switch(count)   {   case 1: return “Welcome to Acme Services<SALT:value>txtFirstName.value</SALT:value>. Please select the Email,Calendar or Stock service.”;   case 2: return “Welcome Please select theEmail, Calendar or Stock service.”;   case 3: return “Welcome Pleaseselect the Email, Calendar or Stock service.”;   default: return “I'msorry <SALT:value>txtFirstName.value</SALT:value>, we're havingcommunication problems. Good Bye.”;   } } </script>

[1423] The next example shows how to use the lastCommandOrExceptionparameter to modify a prompt based upon a event previous event in thedialog. The scenario is:

[1424] A user is asked to provide the name of a departing airport. TheQA contains a Prompt object that is built to handle the initial prompt,a prompt if the user asks for help, and a prompt if the user fails torespond (i.e. a timeout occurs). <speech:qa id=“qa1” runat=“server”>  <Prompt id=“prompt1”   PromptSelectFunction=“SelectDepartingAirport”/>   <Reco id=“reco1” mode=“automatic”>     <Grammars>      <speech:grammar id=“gram1”     src=“http://mysite/NYAirport.xml”      runat=“server” />     </Grammars>   </Reco> <Answers>    <speech:answer id=“ans1” SemanticItem=“siAns1”          runat=“server” />   </Answers> </speech:qa> <speech:commandid=“command1” runat=“server” XpathTrigger=“/sml/help”    scope=“qa1”type=“HELP”>   <Grammar src=“http://mysite/help.xml” runat=“server” /></speech:command> <script> functionSelectDepartingAirport(lastCommandOrException, count, assocArray) {   if(count==1) return “From which airport would you like to depart?”;switch(lastCommandOrException) {   case “SILENCE”: return “I'm sorry Ididn't catch that. From which airport would you like to depart?”;   case“HELP”:    return “You may choose from Kennedy, La Guardia, or thatlittle airport on Long Island. From which airport would you like todepart?”;   default return “What we have here is a failure tocommunicate. Good bye.”;   } } </script>

[1425] The last example shows how to use the assocArray parameter tomodify a prompt during a confirmation pass. The scenario is:

[1426] The user is asked to provide itinerary details: departing andarrival cities and travel date. The QA is constructed to implicitlyconfirm the departing and arrival city information and explicitlyconfirm the travel date. The Prompt object is built to provideappropriate prompting of items requiring confirmation. <speech:qaid=“qa1” runat=“server”>   <Prompt id=“prompt1” InLinePrompt=“What isyour desired        itinerary?”></Prompt>   <Reco id=“reco1”mode=“Automatic”>     <Grammars>       <speech:grammar id=“grm1”            src=“http://mysite/city_date.xml”               runat=“server” />     </Grammars>   </Reco>   <Answers>  <speech:answer id=“A1” XpathTrigger=“/sml/departCity”  SemanticItem=“siTb1” ConfirmThreshold=“0.90” runat=“server” />  <speech:answer id=“A2” XpathTrigger=“/sml/arrivalCity”  SemanticItem=“siTb2” ConfirmThreshold=“0.90” runat=“server” />  <speech:answer id=“A3” XpathTrigger=“/sml/departDate”  SemanticItem=“siTb3” ConfirmThreshold=“1.00” runat=“server” />  </Answers> </speech:qa> <speech:qa id=“qa2” runat=“server”XpathDenyConfirms=“/sml/deny” XpathAcceptConfirms=“/sml/accept”>  <Prompt id=“prompt2” PromptSelectFunction=“myPromptFunction” />  <Reco id=“reco2” mode=“automatic”>     <Grammars>      <speech:grammar id=“grm2”  src=“http://mysite/cityANDdateANDyes_no.xml”       runat=“server” />    </Grammars>   </Reco>   <Confirms>   <speech:answer id=“conf1”XpathTrigger=“/sml/departCity”  SemanticItem=“siTb1”ConfirmThreshold=“0.90” runat=“server” />   <speech:answer id=“conf2”XpathTrigger=“/sml/arrivalCity”  SemanticItem=“siTb2”ConfirmThreshold=“0.90” runat=“server” />   <speech:answer id=“conf3”XpathTrigger=“/sml/departDate”   SemanticItem=“siTb2”ConfirmThreshold=“1.00” runat=“server” />   </Confirms> </speech:qa><script> function myPromptFunction(lastCommandOrException, count,assocArray) { var promptext = “Did you say ”;  if (assocArray[“siTb1”]!=null && assocArray[“siTb1”] !=“”)  {   promptText += “from” +assocArray[“siTb1”];   return promptText;  }  if (assocArray[“siTb2”]!=null && assocArray[“siTb2”] !=“”)  {   promptText += “to” +assocArray[“siTb2”];   return promptText;  }  if (assocArray[“siTb1”]!=null && assocArray[“siTb3”] !=“”)  {   promptText += “on” +assocArray[“siTb3”];   return promptText;  } } </script> class Prompt :Control {   string id{get; set;};   string type{get; set;};   boolprefetch{get; set;};   string lang{get; set;};   bool bargein{get;set;};   string src{get; set;};   string PromptSelectFunction{get;set;};   string OnClientBookmark{get; set;};   string OnClientError{get;set;};   string InlinePrompt{get; set;};   string StyleReference{get;set;};   ParamCollection  Params{get; set:}; }

[1427] 15.1 Prompt Properties

[1428] All properties of the Prompt object are available at design time.

[1429] Type

[1430] Optional. Only used in voice-only mode. The mime-typecorresponding to the speech output format used. No default value. Thetype attribute mirrors the type attribute on the SALT Prompt object.

[1431] Prefetch

[1432] Optional. Only used in voice-only mode. Flag to indicate whetherthe prompt should be immediately synthesized and cached at browser whenthe page is loaded. Default value is false. The prefetch attributemirrors the prefetch attribute on the SALT Prompt object.

[1433] Lang

[1434] Optional. Only used in voice-only mode. Specifies the language ofthe prompt content. The value of this attribute follows the RFC xml:langdefinition. Example: lang=“en-us” denotes US English. No default value.If specified, this over-rides the value set in the Web.config file. Thelang attribute mirrors the lang attribute on the SALT Prompt object.

[1435] Bargein

[1436] Optional. Used only for voice-only mode. Flag that indicateswhether or not the speech platform is responsible for stopping promptplayback when speech or DTMF input is detected. If true, the platformwill stop the prompt in response to input and flush the prompt queue. Iffalse, the platform will take no default action. If unspecified, defaultto true.

[1437] PromptSelectFunction

[1438] Optional. Only used in voice-only mode. Specifies a client-sidefunction that allows authors to select and/or modify a prompt stringprior to playback. The function returns the prompt string.PromptSelectFunction is called once the QA has been activated and beforethe prompt playback begins. If PromptSelectFunction is specified, srcand InLinePrompt are ignored.

[1439] The signature for PromptSelectFunction is as follows:

[1440] String PromptSelectFunction(string lastCommandOrException, intCount, object SemanticItemList)

[1441] where:

[1442] lastCommandOrException is a Command type (e.g., “Help”) or a Recoevent (e.g., “Silence” or “NoReco”).

[1443] Count is the number of times the QA has been activatedconsecutively. Count starts at 1 and has no limit.

[1444] SemanticItemList For voice-only mode, SemanticItemList is anassociative array that maps semantic item id to semantic item objects.For multimodal, SemanticItemList will be null.

[1445] If the PromptSelectFunction is being called from within a Promptobject specified by a CustomValidator control, the SemanticItemList willcontain the SemanticItem being validated.

[1446] If the PromptSelectFunction is being called from within a Promptobject specified by a CompareValidator control, the SemanticItemListwill contain the SemanticItem being validated and (if specified) theSemanticItem to which it is being compared.

[1447] OnClientBookmark

[1448] Optional. Only used in voice-only mode. Specifies a client sidefunction which is called when a Bookmark is reached in the prompt textduring playback. The function does not return a value. The signature forOnClientBookmark is as follows:

[1449] function OnClientBookmark( )

[1450] OnClientError

[1451] Optional. Only used in voice-only mode. Specifies a client sidefunction which is called in response to an error event in the client.Error events are generated from the event object. The function returns aBoolean value. The RunSpeech algorithm will continue executing if anOnClientError script returns true. The RunSpeech algorithm will navigateto the default error page specified in the Web.config file if anOnClientError script returns false or if an error occurs and theOnClientError function is not specified. When navigating to the errorpage, both status and description will be passed in the query string.For example, if the error page is http://myErrorPage, we will navigateto http://myErrorPage?status=X&description=Y (where X is the status codeassociated with the error and Y is the description of that error givenin the Speech Tags Specification. The signature for OnClientError is asfollows:

[1452] bool OnClientError(int status)

[1453] where status is the code returned in the event object.

[1454] Note: For the SDK Beta release, it is advisable to specify adefault error page using the syntax described in Section 5 GlobalApplication Settings

[1455] InlinePrompt

[1456] Optional. Only used in voice-only mode. The text of th prompt tobe played. It may contain further markup, as in TTS renderinginformation, or <value>elements. If a PromptSelectFunction function isspecified, the InlinePrompt is ignored.

[1457] StyleReference

[1458] Optional. Used in both multimodal and voice-only modes. Specifiesthe name of a Style object. At render time, the Prompt object willsearch for the named Style control and will use any property valuesspecified on the Style as default values for its own properties.Explicitly set property values by the Prompt object will override thoseset on the referenced Style.

[1459] Params

[1460] Optional. An collection of param objects that specify additional,non-standard configuration parameter values to the speech platform. Theexact nature of the configurative parameters will differ according tothe proprietary platform used. Values of parameters may be specified inan XML namespace, in order to allow complex or structured values. Anexception will be thrown if the Params collection contains a non-paramobject.

[1461] For example, the following syntax could be used to specify thelocation of a remote prompt engine for distributed architectures:  <Params>    <speech:param name=“promptServer”runat=“server”>//myplatform/promptServer</speech:param>   </Params>

[1462] 16 Reco Object

[1463] Reco is rendered for both multimodal and voice-only modes. TheReco object is used to specify speech input resources and features aswell as provide for the management of cases when vaild recognitionresults are not returned.

[1464] How Reco object is used.

[1465] Voice-Only

[1466] During the processing of the Prompt object, RunSpeech determineswhether or not the currently active QA contains a Reco object. If itdoes, RunSpeech asks the speech platform to start the recognitionprocess using the grammar specified by the Reco's Grammar object.RunSpeech calls the function specified by OnClientListening immediatelyafter activating the Reco's underlying <listen> tag. The recognitionprocess is stopped depending on the value of the mode attribute.RunSpeech processes successful recognition results using informationspecified in the Answer object.

[1467] RunSpeech uses the Reco object to handle the situations when thespeech platform is not able to return valid recognition results, i.e.,speech platform errors, timeouts, silence, or inability of the speechplatform to recognize an utterance. In each of these cases, RunSpeechcalls the appropriate handler (if specified) after setting the value ofthe lastCommandOrException attribute.

[1468] Multimodal

[1469] The Reco object is used by the Multimodal.js client-side scriptjust as it is used by the RunSpeech voice-only client-side script (asdescribed above) with one exception, starting/stopping the recognitionprocess. Multimodal scenarios do not require speech output as amechanism to prompt the user for input. In fact, prompting in speechcontrols is not available in multimodal scenarios as the Prompt objectis not rendered to the client. Therefore, an alternate mechanism isrequired to start the recognition process.

[1470] Multimodal.js uses the event specified in theStartElement/StartEvent attributes to start the recognition process. Thefunction specified by the OnClientListening attribute is called afterthe recognition process has started. Multimodal.js uses the combinationof the StopEvent and mode attributes to stop the recognition process.class Reco : Control {   string id{get; set;};   stringStartElement{get; set;};   string StartEvent{get; set;};   stringStopElement{get; set;};   string StopEvent{get; set;};   intinitialTimeout{get; set;};   int babbleTimeout{get; set;};   intmaxTimeout{get; set;};   int endSilence{get; set;};   float  reject{get; set;};   string mode{get; set;};   string lang{get; set;};  string GrammarSelectFunction{get; set;};   stringOnClientSpeechDetected{get; set;};   string OnClientSilence{get; set;};  string OnClientNoReco{get; set;};   string OnClientError{get; set;};  string   StyleReference{get; set;};   GrammarCollection Grammars{get;set;};   ParamCollection Params{get;set;};   Control   record{get;set;}; }

[1471] 16.1 Reco Properties

[1472] All properties are available at design time.

[1473] Start Element

[1474] Optional, but must be present if StartElement is specified. Usedonly in multimodal mode. Specifies the name of the GUI element withwhich the start of the Reco is associated. See StartEvent. No defaultvalue.

[1475] StartEvent

[1476] Optional, but must be present if StartElement is specified. Onlyused in multimodal mode. Specifies the name of the event that willactivate (start) the underlying client-side Reco object. See startElement No default value.

[1477] Start Element

[1478] Optional, but must be present if StopElement is specified. Usedonly in multimodal mode. Specifies the name of the GUI element withwhich the stop of the Reco is associated. See StopEvent. No defaultValue

[1479] StopEvent

[1480] Optional, but must be present if StartElement is specified. Onlyused in multimodal mode. Specifies the name of the event that will stopthe underlying client-side Reco object. See stop Element. No defaultvalue.

[1481] StartEvent and StopEvent will be used in multi-modalapplications, typically for tap-and-talk interactions. E.g.StartEvent=Button1.onmousedown, StopEvent=Button1.onmouseup.

[1482] StartEvent and StopEvent are allowed to be the same (click tostart, click to stop). However, it is the author's responsibility tode-activate Recos before starting new ones in the case when the end userfires two StartEvents in succession (e.g., click on one control to starta reco then click on a different control to start another reco beforestopping first reco).

[1483] Note: IE requires exact cases when running Jscript.

[1484] Therefore, the the case for event values specified in theStartEvent and StopEvent attributes must be exactly as those events aredefined. For example, the onmouseup and onmousedown events are specifiedin all lower case letters.

[1485] Note: StartEvent and StopEvent are not rendered for voice-onlymode.

[1486] initialTimeout

[1487] Optional. Used in both multimodal and voice-only modes. The maxtime in milliseconds between start of recognition and the detection ofspeech. This value is passed to the recognition platform, and ifexceeded, an onSilence event will be thrown from the recognitionplatform. If not specified, the speech platform will use a defaultvalue. No default value. An exception will be thrown for non-integer ornegative integer value.

[1488] Note: The sum of the initialTimeout and babbleTimeout valuesshould be smaller or equal to the global maxTimeout attribute or theReco attribute maxTimeout (see below) if it is set.

[1489] Note: The initialTimeout attribute mirrors the initialTimeoutattribute on the SALT Reco object.

[1490] babbleTimeout

[1491] Optional. Used in both multimodal and voice-only modes. Optional.The maximum period of time in milliseconds for an utterance. For recosin automatic and single mode, this applies to the period between speechdetection and the speech endpoint or stop call. For recos in ‘multiple’mode, this timeout applies to the period between speech detection andeach phrase recognition—i.e. the period is restarted after each returnof results or other event. If exceeded, the onnoreco event is thrownwith status code −15. This can be used to control when the recognizershould stop processing excessive audio. For automatic mode listens, thiswill happen for exceptionally long utterances, for example, or whenbackground noise is mistakenly interpreted as continuous speech. Forsingle mode listens, this may happen if the user keeps the audio streamopen for an excessive amount of time (eg by holding down the stylus intap-and-talk). If the attribute is not specified, the speech platformwill use a default value. No default value. An exception will be thrownfor non-integer or negative integer values.

[1492] Note: The sum of the initialTimeout and babbleTimeout valuesshould be smaller or equal to the global maxTimeout attribute or theReco attribute maxTimeout (see below) if it is set.

[1493] Note: The babbleTimeout attribute mirrors the babbleTimeoutattribute on the SALT Reco object.

[1494] maxTimeout

[1495] Optional. Used in both multimodal and voice-only modes. Theperiod of time in milliseconds between recognition start and resultsreturned to the browser. If exceeded, an OnError event is thrown by thebrowser—this provides for network or recognizer failure in distributedenvironments. For Recos in “multiple” mode, as with babbleTimeout, theperiod is restarted after the return of each recognition or other event.No default value. An exception will be thrown for non-integer ornegative integer values.

[1496] Note: maxTimeout should be greater than or equal to the sum ofinitialTimeout and babbleTimeout. If specified, the value of thisattribute over-rides the value of maxTimeout set in the Web.config file.No default value.

[1497] Note: The maxTimeout attribute mirrors the maxTimeout attributeon the SALT Reco object.

[1498] endSilence

[1499] Optional. Used in both multimodal and voice-only modes. For Recoobjects in “automatic” mode, the period of silence in milliseconds afterthe end of an utterance which must be free of speech after which therecognition results are returned. Ignored for Recos of modes other than“automatic”. If not specified, defaults to platform internal value. Anexception will be thrown for non-integer or negative integer values.

[1500] Reject

[1501] Optional. Used in both multimodal and voice-only modes. Specifiesthe rejection threshold, below which the platform will throw the noRecoevent. If not specified, the speech platform will use an internaldefault value. Legal values are 0-1 and are platform specific. Anexception will be thrown for out of range reject values. Default is 0.

[1502] Lang

[1503] Optional. Used in both multimodal and voice-only modes. Specifiesthe language of the speech recognition engine. The value of thisattribute follows the RFC xml:lang definition. Example: lang=“en-us”denotes US English. No default value. This over-rides the global settingin the Web.config file. The lang attribute mirrors the lang attribute onthe SALT Reco object.

[1504] Mode

[1505] Optional. Used in both multimodal and voice-only modes. Specifiesthe recognition mode to be followed. Default is “automatic”. Legalvalues are “automatic”, “single”, and “multiple”.

[1506] Mode=“Automatic”

[1507] Used for recognitions in telephony scenarios. The speech platformitself (not the application) is in control of when to stop therecognition process. Mode=“automatic” is the only mode setting thatworks in voice-only, other modes will be ignored and “automatic” will beused.

[1508] Mode=“Single”

[1509] Used for multimodal (tap-to-talk) scenarios. The return of arecognition result is under the control of an explicit call to stop therecognition process by the application. However, exceeding babbleTimeoutor maxTimeout will stop recognition. Mode=“single” is ignored forvoice-only.

[1510] Mode-“Multiple”

[1511] Used for “open-microphone” or dictation scenarios. Recognitionresults are returned at intervals until the application makes anexplicit call to stop the recognition process (or babbleTimeout ormaxTimeout periods are exceeded). Multiple mode recos are not supportedin voice-only mode dialogs. If the browser is a voice-only browser andreco mode is set to “multiple”, an exception will be thrown at rendertime. Mode=“multiple” is ignored for voice-only.

[1512] GrammarSelectFunction

[1513] Optional. Used in both multimodal and voice-only modes. Specifiesa client-side script that will be called prior to starting therecognition process. The script is written by the dialog author and maybe used to select or modify the Grammar objects associated with the Recoobject. The script may also be used to adjust speech recognitionfeatures or confidence/rejection thresholds. The GrammarSelectFunctionfunction does not return values. The signature for GrammarSelectFunctionis as follows:

[1514] function GrammarSelectFunction(object recoObj, stringlastCommandOrException, int Count, object SemanticItemList)

[1515] where:

[1516] recoObj is the Reco object about to start.

[1517] lastCommandOrException is a Command type (e.g., “Help”) or a Recoevent (e.g., “Silence” or “NoReco”). For multimodal dialogs,lastCommandOrException will be an empty string Count is the number oftimes the QA containing the Reco object has been activatedconsecutively. Count starts at 1 and has no limit. For multimodaldialogs, count will be zero.

[1518] SemanticItemList For voice-only mode, SemanticItemList is anassociative array that maps semantic item id to semantic item objects.For multimodal dialogs, SemanticItemList will be null.

[1519] OnClientSpeechDetected

[1520] Optional. Used in both multimodal and voice-only modes. Specifiesa client-side script function that will be called when theonspeechdetected event is fired by the speech recognition platform onthe detection of speech. Determining the actual time of firing is leftto the platform (which may be configured on certain platforms using the<param> element. This may be anywhere between simple energy detection(early) or complete phrase or semantic value recognition (late). Thisevent also triggers onbargein on a prompt which is in play and maydisable the initial timeout of a started dtmf object. This function canbe used in multimodal scenarios, for example, to generate a graphicalindication that recognition is occurring, or in voice-only scenarios toenable fine control over other processes underway during recognition.The function does not return any values. The signature forOnClientSpeechDetected is as follows:

[1521] function OnClientSpeechDetected( )

[1522] If a Dtmf object is active when the OnClientSpeechDetectedfunction is called, the timeouts of the Dtmf object will be disabled.

[1523] OnClientSilence

[1524] Optional. Used in both multimodal and voice-only modes. Specifiesa client-side script that will be called after detecting silence (inresponse to SALT reco onSilence event). The function does not return anyvalues. The signature for OnClientSilence is as follows:

[1525] function OnClientSilence(int status)

[1526] where status is the code returned in the event object.

[1527] If a Dtmf object is active when the OnClientSilence function iscalled, the Dtmf object will be stopped.

[1528] OnClientNoReco

[1529] Optional. Used in both multimodal and voice-only modes. Specifiesa client-side script that will be called after detecting no recognition(in response to SALT reco onNoReco event). The function does not returnany values. The signature for OnClientNoReco is as follows:

[1530] function OnClientNoReco(int status)

[1531] where status is the code returned in the event object.

[1532] If a Dtmf object is active when the OnClientNoReco function iscalled, the Dtmf object will be stopped.

[1533] OnClientError

[1534] Optional. Used in both multimodal and voice-only modes. Specifiesa client side function which is called in response to an error event inthe client. Error events are generated from the event object. Thefunction returns a boolean value. The RunSpeech algorithm will continueexecuting if an OnClientError script returns true. The RunSpeechalgorithm will navigate to the default error page specified in theWeb.config file if an OnClientError script returns false or if an erroroccurs and the OnClientError function is not specified. When navigatingto the error page, both status and description will be passed in thequery string. For example, if the error page is http://myErrorPage, wewill navigate to http://myErrorPage?status=X&description=Y (where X isthe status code associated with the error and Y is the description ofthat error given in the Speech Tags Specification. The signature forOnClientError is as follows:

[1535] bool OnClientError(int status)

[1536] where status is the code returned in the event object.

[1537] Note: the return value of OnClientError is ignored in multimodalmode.

[1538] If a Dtmf object is active when the OnClientError function iscalled, the Dtmf object will be stopped.

[1539] StyleReference

[1540] Optional. Used in both multimodal and voice-only modes. Specifiesthe name of a Style object. At render time, the Reco object will searchfor the named Style control and will use any property values specifiedon the Style as default values for its own properties. Explicitly setproperty values by the Reco object will override those set on thereferenced Style.

[1541] Grammars

[1542] Optional. An array of grammar objects as specified below. Anexception will be thrown if a Grammars collection contains a non-grammarobject.

[1543] Params

[1544] Optional. Used in both multimodal and voice-only modes. Ancollection of param objects that specify additional, non-standardconfiguration parameter values to the speech platform. The exact natureof the configurative parameters will differ according to the proprietaryplatform used. Values of parameters may be specified in an XMLnamespace, in order to allow complex or structured values. An exceptionwill be thrown if the Params collection contains a non-param object.

[1545] For example, the following syntax could be used to specify thelocation of a remote speech recognition server for distributedarchitectures: <Params>  <speech:param          name=“recoServer”runat=“server”>//myplatform/recoServer</speech:param> </Params>

[1546] Record

[1547] Optional. Used in both multimodal and voice-only modes. Therecord object is used for recording audio input from the user. Recordingmay be used in addition to recognition or in place of it, according tothe abilities of the platform and its profile. Only one record object ispermitted in a single <reco>.

[1548] 17 Grammar Object

[1549] The grammar object contains information on the selection andcontent of grammars, and the means for processing recognition results.All the properties defined are read/write properties. class Grammar :Control {   string  id{get; set;};   string  type{get; set;};  string  lang{get; set;};   string  src{get; set;};  string  InLineGrammar{get; set;};   string  StyleReference{get; set;};}

[1550] 17.1 Grammar Properties

[1551] Grammar is rendered for both multimodal and voice-only modes. Allproperties are available at design time and run time.

[1552] Type

[1553] Optional. Used in both multimodal and voice-only modes. Themime-type corresponding to the grammar format used. No default value.The type attribute mirrors the type attribute on the SALT Grammarobject.

[1554] Lang

[1555] Optional. Used in both multimodal and voice-only modes. Stringindicating which language the grammar refers to. The value of thisattribute follows the RFC xml:lang definition. Example: lang=“en-us”denotes US English. No default value. Over-rides the global value set inthe Web.config file. The lang attribute mirrors the lang attribute onthe SALT Grammar object.

[1556] src

[1557] Optional. Used in both multimodal and voice-only modes. Specifiesthe URI of the grammar to load. If an inline grammar and src are bothspecified the inline grammar takes precendence and src is ignored. Thesrc attribute mirrors the src attribute on the SALT Grammar object. Anexception will be thrown if one of src or InlineGrammar is notspecified.

[1558] InlineGrammar

[1559] Optional. Used in both multimodal and voice-only modesInlineGrammar accesses the text of the grammar specified inline. IfInlineGrammar and src are both specified, InlineGrammar takesprecendence and src is ignored. An exception will be thrown if one ofsrc or InlineGrammar is not specified.

[1560] Inline grammars must be HTML Encoded, they are HTML encoded whensent down to the server. Authors must use &gt for > and &lt for < andadhere to all other HTML Encoding standards. It is recommended thatauthors use the property builder in DET, which will handle the HTMLencoding automatically.

[1561] StyleReference

[1562] Optional. Used in both multimodal and voice-only modes. Specifiesthe name of a Style object. At render time, the Grammar object willsearch for the named Style control and will use any property valuesspecified on the Style as default values for its own properties.Explicitly set property values by the Grammar object will override thoseset on the referenced Style.

[1563] 18 Dtmf Object

[1564] Dtmf may be used by QA controls in telephony applications. TheDtmf object essentially applies a different modality of grammar (akeypad input grammar rather than a speech input grammar) to the samequestion. class Dtmf : Control { string id{get; set;}; boolpreflush{get; set;}; int initialTimeOut{get; set;}; intinterDigitTimeOut{get; set;}; int endSilence{get; set;}; stringOnClientSilence{get; set;}; string OnClientKeyPress{get; set;}; stringOnClientError{get; set;}; string StyleReference{get; set;};ParamCollection Params{get; set;}; GrammarCollection Grammars{get;set;};}

[1565] 18.1 Dtmf Properties

[1566] All properties are available at design time.

[1567] Preflush

[1568] Optional. Flag to indicate whether to automatically flush theDTMF buffer on the underlying telephony interface card beforeactivation. Default is “false” (to enable type-ahead functionality). Thepreflush attribute mirrors the preflush attribute on the SALT DTMFobject.

[1569] InitialTimeOut

[1570] Optional. The number of milliseconds to wait for receiving thefirst key press before raising a timeout event. If this timeout occursthe DTMF collection end automatically. If unspecified, initialTimeoutdefaults to a telephony platform internal setting. An exception isthrown if initialTimeout is a negative value. The initialTimeoutattribute mirrors the initialTimeout attribute on the SALT DTMF object.

[1571] InterdigitTimeout

[1572] Optional. The timeout period in milliseconds for adjacent DTMFpresses before raising a timeout event. If this timeout occurs the DTMFcollection ends automatically. If unspecified, interdigitTimeoutdefaults to a telephony platform internal setting. An exception isthrown if initialTimeout is a negative value. The interdigitTimeoutattribute mirrors the interdigitTimeout attribute on the SALT DTMFobject.

[1573] EndSilence

[1574] Optional. The timeout period in milliseconds when input matches acomplete path through the grammar but further input is still possible.This timeout specifies the period of time in which further input ispermitted after the complete match. Once exceeded, onreco is thrown.(For a complete grammar match where further input is not possible, theendsilence period is not required, and onreco is thrown immediately.) Ifthis attribute is not supported directly by a platform, or unspecifiedin the application, the value of endsilence defaults to that used forinterdigittimeout. An exception is thrown if endSilence is a negativevalue.

[1575] OnClientSilence

[1576] Optional. Specifies a client-side script function to be called ifthere is no DTMF key press before initialTimeout expires. The platformhalts DTMF collection automatically. The QA treats this as a silence.The function returns no values. The signature for OnClientSilence is asfollows:

[1577] function OnClientSilence( )

[1578] If a Reco object is active when the OnClientSilence function iscalled, the Reco object will be stopped.

[1579] OnClientKeyPress

[1580] Optional. Specifies a client-side script function that is calledon every pressing of a DTMF key which is legal according to the inputgrammar. If a prompt is in playback, the onkeypress event will triggerthe onbargein event on the prompt (and cease its playback if theprompt's bargein attribute is set to true). If a Reco object is active,the first onkeypress event will disable the timeouts of the Reco object.

[1581] OnClientError

[1582] Optional. Specifies a client-side function which is called inresponse to a serious or fatal error with the DTMFcollection/recognition process. Error events are generated from theevent object. The function returns a boolean value. The RunSpeechalgorithm will continue executing if an OnClientError script returnstrue. The RunSpeech algorithm will navigate to the default error pagespecified in the Web.config file if an OnClientError script returnsfalse or if an error occurs and the OnClientError function is notspecified. When navigating to the error page, both status anddescription will be passed in the query string. For example, if theerror page is http://myErrorPage, we will navigate tohttp://myErrorPage?status=X&description=Y (where X is the status codeassociated with the error and Y is the description of that error givenin the Speech Tags Specification. The signature for OnClientError is asfollows:

[1583] bool OnClientError(int status)

[1584] where status is the code returned in the event object.

[1585] If a Reco object is active when the OnClientError function iscalled, the Reco object will be stopped.

[1586] OnClientNoReco

[1587] Optional. Specifies a client side function which is called inresponse to a failure to recognize by the DTMF collection/recognitionprocess. This is most lokely to occur when the input detected does notmatch an path through the active grammars. The function does not need toreturn a value. The prototype for the function is:

[1588] OnClientNoReco(int status)

[1589] Where status is the code returned the in the event object.

[1590] StyleReference

[1591] Optional. Used in both multimodal and voice-only modes. Specifiesthe name of a Style object. At render time, the Dtmf object will searchfor the named Style control and will use any property values specifiedon the Style as default values for its own properties. Explicitly setproperty values by the Dtmf object will override those set on thereferenced Style.

[1592] Grammars

[1593] Optional. An array of grammar objects.

[1594] Params

[1595] An collection of param objects that specify additional,non-standard configuration parameter values to the speech platform. Theexact nature of the configurative parameters will differ according tothe proprietary platform used. Values of parameters may be specified inan XML namespace, in order to allow complex or structured values. Anexception will be thrown if the Params collection contains a non-paramobject.

[1596] For example, the following syntax shows how to specify aparameter on particular DTMF platform.

[1597] <Params>   <speech:param  name=“myDTMFParam”  runat=“server”>myDTMFValue </speech:param> </Params>

[1598] 19 Param Object

[1599] The param object allows authors to specify the names and valuesof additional, non-standard configuration parameters to the speechplatform. The exact nature of the configurative parameters will differaccording to the proprietary platform used. Values of parameters may bespecified in an XML namespace, in order to allow complex or structuredvalues. class param : Control {   string  name{get; set;};  string  Value{get; set;}; }

[1600] 19.1 Param Properties

[1601] Name

[1602] Required. The name of the parameter to be configured. Anexception will be thrown for <param>elements that do not contain thename attribute.

[1603] Value

[1604] Optional. The value which will be assigned to the namedparameter.

[1605] 20 Record Object

[1606] The record object is used to record audio input from the user.Recording may be used in addition to recognition or in place of it,according to the abilities of the platform and its profile. class record: Control {   bool      enabled{get; set;};   string     type{get;set;};   bool      beep{get; set;}; }

[1607] 20.1 Record Properties

[1608] Enabled

[1609] Optional. Flag to indicate whether or not to record the userinput. Defaults to “false”.

[1610] Type

[1611] Optional. MIME type of the recording. MIME types can be specifiedsuch as “audio/wav” for WAV (RIFF header) 8 kHz 8-bit mono mu-law [PCM]single channel or “audio/basic” for Raw (headerless) 8 kHz 8-bit monomu-law [PCM] single channel. If unspecified, defaults to G.711 wavefile.

[1612] Beep

[1613] Optional. Boolean value, if true, the platform will play a beepbefore recording begins. Defaults to false.

[1614] 21 Call Control

[1615] All call-related server-side controls deal with a single deviceand a single active call at any given time. If the dialog author needsto monitor more than one device or handle more than one active call, thecustom SmexMessage can be used and the author will have to handle CSTAmessages.

[1616] All call control controls are only used in voice-only mode. TheSpeechContrbls.dll will implement a support class (CallInfo), a baseclass (SmexMessageBase), and the following WebControls: SmexMessage   ofor custom / advanced CSTA messages, and messages    to any non-CSTA<smex> elements by specifying a    client side <smex> elementTransferCall   o for CSTA SingleStepTransfer service MakeCall   o forCSTA MakeCall service DisconnectCall   o for CSTA ClearConnectionservice AnswerCall   o for CSTA AnswerCall service

[1617] 21.1 Common Classes

[1618] 21.1.1 CallInfo class CallInfo {   string MonitorCrossRefId{get;};   string DeviceId {get;};   string CallId {get;};   stringCallingDevice {get;};   string CalledDevice {get;}; }

[1619] 21.1.1.1 CallInfo Properties

[1620] MonitorCrossRefId: The id returned by the start page'sMonitorStart.

[1621] DeviceId: The device id for the current active call.

[1622] CallId: The call id for the current active call. These propertiescan be used in the custom SmexMessage object to form the correct CSTAxml message on the web server side.

[1623] CallingDevice: This represents the calling device informationprovided by the network (ANI, for example). This information will alwaysremain with the call and will never change (unlike the callingDevice).

[1624] CalledDevice: This represents the called device informationprovided by the network (DNIS, for example). This information willalways remain with the call and will never change (unlike thecalledDevice).

[1625] 21.1.2 SmexMessageBase

[1626] This is an internal class. Authors that need to create newcall-control controls should derive from SmexMessage. internal classabstract SmexMessageBase { string ID {get; set }; int Timer (get; set};bool AutoPostback {get; set}; string ClientActivationFunction {get;set}); string OnClientError {get, set}; string OnClientTimeout {get;set}; CallInfo CurrentCall {get; } }

[1627] 21.1.2.1 SmexMessageBase Properties

[1628] ID: ASP.NET control ids.

[1629] SpeechIndex: Same as for other speech controls controls. Thisindex controls the order of the object within RunSpeech. Default 0,meaning source order after all non-zero indexed speech objects.

[1630] Timer: Number in milliseconds indicating the time span before atimeout event will be triggered. This set on the client side<smex>object before the CSTA message is sent. The default is 0, meaningno timeout. An exception will be thrown for neagtive values of Timer.

[1631] AutoPostback: Whether to cause a postback when the object's eventis fired. Default is false.

[1632] ClientActivationFunction: The client side function called byRunSpeech to determine whether an object is active. When not specified,the object is considered active only once (the PlayOnce behavior).ClientActivationFunction returns a bool to indicate whether theassociated object should be active (true) or not (false). The signaturefor ClientActivationFunction is:

[1633] function ClientActivationFunction(object sender)

[1634] where sender is the current object

[1635] OnClientError: Optional. Default is false when not specified. Theclient side function called when <smex> fires the onerror event.OnClientError returns a bool—true to continue RunSpeech and false to goto the error page. The signature for OnClientError is:

[1636] function OnClientError(object sender, int status)

[1637] where

[1638] sender is the current object, and

[1639] status is the value of the object's status property.

[1640] OnClientTimeout: Optional. Default is true when not specified.The client side function called when <smex> fires the ontimeout event.OnClientTimeout returns a bool—true to continue RunSpeech and false togo to the error page. The signature for OnClientTimeout is:

[1641] function OnClientTimeout(object sender

[1642] where

[1643] sender is the current object.

[1644] CurrentCall: Returns the current active call object.

[1645] 21.2 Server-Side Classes

[1646] 21.2.1 SmexMessage

[1647] This is a generic class for sending raw CSTA messages andreceiving CSTA events.

[1648] Since the number and types of events generated by this message isunknown, the author needs to be careful about when RunSpeech cancontinue.

[1649] RunSpeech will be paused just before calling author'sOnClientBeforeSend function when the message is about to be sent.

[1650] If OnClientReceive is not specified, RunSpeech will resume whenany smex event is received after message is sent.

[1651] If OnClientReceive is specified, the author returns true toindicate RunSpeech can resume after receiving the expected event.

[1652] RunSpeech will resume after Error or Timeout happens.

[1653] The Smex Timer will be set to the given value before the messageis sent and back to zero right before RunSpeech resumes.

[1654] When an unexpected smex event arrives, i.e. when the currentactive object in RunSpeech is not a call related object, the smex eventis ignored.

[1655] When AutoPostback is set to true, all events will execute theclient handler, then cause a post-back to the web server where thecorresponding server event will be fired. class SmexMessage :SmexMessageBase {   string Message {get; set};   string ClientSmexId{get; set};   string OnClientBeforeSend {get; set};   stringOnClientReceive {get; set};   event Receive; }

[1656] 21.2.1.1 SmexMessage Properties

[1657] Message: Required. The CSTA XML message to be sent. An exceptionwill be thrown if Message is not specified.

[1658] OnClientBeforeSend: Optional. Client side function called justbefore the message is sent. This is to give the author a last chance tomodify the message. OnClientBeforeSend returns a string containing thenew message. If null is returned, original message will be sent. Thesignature for OnClientBeforeSend is:

[1659] function OnClientBeforeSend(object sender, string Message

[1660] where:

[1661] sender is the client-side SmexMessage object, and

[1662] Message is the original message.

[1663] Receive: Optional. Server side event when client side<smex>object receives smex events. The signature of aReceiveEventHandler is:

[1664] void ReceiveEventHandler(object sender, ReceiveEventArgs e)

[1665] where

[1666] sender will be the server side SmexMessage object. The secondargument e is of following type: class ReceiveEventArgs : EventArgs {  string  Received {get}; }

[1667] where

[1668] Received contains the event message received from <smex>.

[1669] OnClientReceive: Optional. Client-side function called whenclient side <smex>object receives smex events. OnClientReceive returns abool—true means that this object has got all the events and RunSpeechcan continue, false means that this object expects more events beforeRunSpeech can continue. The signature for OnClientReceive is:

[1670] function OnClientReceive(object sender, string Message)

[1671] where

[1672] sender is the client-side SmexMessage object, and

[1673] Message is the received message.

[1674] ClientSmexId: Optional. This is the client side <smex> elementid. If not set, messages will be sent through the default Call Manager<smex> element. If set to, non-empty string, it has be to be id of anexisting SALT <smex> element, which the author has to add to the page.

[1675] 21.2.2 TransferCall

[1676] The TransferCall control transfers the current call using CSTASingleStepTransfer service. When RunSpeech runs this object, it blocksany further speech dialog until transfer succeeds or fails. classTransferCall : SmexMessageBase { string TransferredTo {get; set}; stringOnClientFailed {get; set}; string OnClientTransferred {get; set}; eventTransferred; }

[1677] 21.2.2.1 TransferCall Properties

[1678] TransferredTo: Required. The device identifier associated withthe transferred to endpoint.

[1679] Transferred: Optional. Server side event fired when the call istransferred. The signature of an EventHandler is:

[1680] void EventHandler(object sender, EventArgs e);

[1681] where

[1682] sender is the server side TransferCall object, and

[1683] e is of the standard EventArgs type.

[1684] OnClientTransferred: Optional. Client side function called whenthe call is transferred. OnClientTransferred returns nothing. Thesignature of OnClientTransferred is

[1685] function OnClientTransferred(object sender)

[1686] where:

[1687] sender is the client-side TransferCall object.

[1688] OnClientFailed: Client-side function called when CSTA returnsFAILED event. OnClientFailed returns a bool—true to continue RunSpeechand false to go to error page. The signature for OnClientFailed is:

[1689] function OnClientFailed(object sender, string cause)

[1690] where

[1691] sender is the client-side TransferCall object, and

[1692] cause is the reason for failure returned from <smex>.

[1693] 21.2.3 MakeCall

[1694] The MakeCall control makes an outbound call to the given numberon the given device when RunSpeech runs this object. Further speechdialog is blocked until the call is connected or fails to connect. classMakeCall : SmexMessageBase { string CallingDevice {get; set} stringCalledDirectoryNumber {get; set}; string OnClientFailed {get; set};string OnClientConnected {get; set); event Connected; }

[1695] 21.2.3.1 MakeCall Properties

[1696] CallingDevice: Required. Default is the internal CallInforDeviceId. The control will use this device to place the outbound call.

[1697] CalledDirectoryNumber: Required. Phone number to dial. Anexception will be thrown if CalledDirectoryNumber is not specified.

[1698] Connected: Server side event when the call is connected.

[1699] The signature of an EventHandler is:

[1700] void EventHandler(object sender, EventArgs e)

[1701] where

[1702] sender is the server side MakeCall object, and

[1703] e is of the standard EventArgs type.

[1704] At this point, the CurrentCall property should contain theinformation about the call in progress.

[1705] OnClientConnected: Client side function called when the call isconnected. OnClientConnected returns nothing. The signature forOnClientConnected is:

[1706] function OnClientConnected(object sender, stringCalledDirectoryNumber

[1707] where:

[1708] sender is the client-side MakeCall object, and

[1709] CalledDirectoryNumber is the property of the MakeCall object.

[1710] OnClientFailed: Client side function called when CSTA returnsFAILED event. OnClientFailed returns a bool—true to continue RunSpeechand false to goto error page. The signature for OnClientfailed is:

[1711] function OnClientFailed(object sender, string cause)

[1712] where

[1713] sender is the client-side MakeCall object, and

[1714] cause is the reason for failure returned from <smex>.

[1715] 21.2.4 DisconnectCall class DisconnectCall : SmexMessageBase {string OnClientFailed {get; set}; string OnClientDisconnected {get;set}; event Disconnected; }

[1716] 21.2.4.1 DisconnectCall Properties

[1717] Disconnected: Optional. Server side event when the call isdisconnected. The signature of an EventHandler is:

[1718] void EventHander(object sender, EventArgs e)

[1719] where:

[1720] sender is the server side DisconnectCall object and,

[1721] e is of the standard EventArgs type.

[1722] OnClientDisconnected: Optional. Client side function called whenthe call is disconnected. OnClientDisconnected returns nothing. Thesignature for OnClientDisconnected is:

[1723] function OnClientDisconnected(object sender)

[1724] where sender is the client-side Disconnect Call object.

[1725] OnClientFailed: Optional. Client side function called when CSTAreturns FAILED event. OnClientailed returns a bool true to continueRunSpeech and false to goto error page. The signature for OnClientFailedis:

[1726] function OnClientFailed(object sender, string cause)

[1727] where

[1728] sender is the client-side Disconnect Call object, and

[1729] cause is the reason for failure returned from <smex>.

[1730] 21.2.5 AnswerCall

[1731] The AnswerCall control answers incoming calls on the givendevice. When activated, this object will block RunSpeech until anincoming call is answered.

[1732] Server-Side Class: class AnswerCall : SmexMessageBase { stringOnClientConnected {get; set}; string OnClientFailed {get; set}; eventConnected; }

[1733] 21.2.5.1 AnswerCall Properties

[1734] Connected: Optional. Server side event when the call isconnected. The signature of a ConnectedEventHandler is:

[1735] void EventHandler(object sender, EventArgs e)

[1736] where:

[1737] sender is the server side AnswerCall object and

[1738] e is of the standard EventArgs type.

[1739] At this point, the CurrentCall property should containinformation of the call in progress.

[1740] OnClientConnected: Optional. Client side function called when thecall is connected. OnClientConnected returns nothing. The signature forOnClientConected is:

[1741] function OnClientConnected(object sender, string callid, stringCallingDevice, string CalledDevice)

[1742] where:

[1743] sender is the client side AnswerCall object

[1744] callid is the id of the current call

[1745] CallingDevice is the caller's network device id

[1746] CalledDevice is the recipient's network device id.

[1747] OnClientFailed: Optional. Client side function called when CSTAreturns FAILED event. OnClientFailed returns a bool—true to continueRunSpeech and false to go to error page. The signature of OnClientFailedis:

[1748] function OnClientFailed(object sender, string cause)

[1749] where

[1750] sender is the client-side AnswerCall object.

[1751] cause is the reason for failure returned from <smex>.

[1752] 22 RunSpeech

[1753] 22.1 Dialog Processing Algorithm

[1754] The RunSpeech algorithm is used to drive dialog flow on avoice-only client. This involves system prompting and dialog managementand processing of speech input. It is specified as a script filereferenced by URI from every relevant speech-enabled page (equivalent toinline embedded script)

[1755] Important: the RunSpeech script will be completely exposed to thepublic. Since it will be hosted on the application web site, authors ofdialogs will be at liberty to examine, edit, replace or ignore theRunSpeech script code.

[1756] Rendering of the page for voice only browsers is done in thefollowing manner:

[1757] The RunSpeech function works as follows (RunSpeech is called inresponse to document.onreadystate becoming “complete”):

[1758] Controls considered for activation are the QA, CompareValidatorand CustomValidator controls.

[1759] 1. Find the first active QA or Validator control in speech indexorder (determining whether a QA/Validator is active is explained below).

[1760] 2. If there is no active control, submit the page.

[1761] 3. Otherwise, run the control.

[1762] A QA is considered active if and only if:

[1763] 1. The QA's clientActivationFunction either is not present orreturns true, AND

[1764] 2. If the Answers collection is non empty, the State of at leastone of the SemanticItems pointed to by the set of Answers is Empty OR

[1765] 3. If the Answers collection is empty, the State at least oneSemanticItem in the Confirm array is NeedsConfirmation.

[1766] However, if the QA has PlayOnce true and its Prompt has been runsuccessfully (reached OnComplete) the QA will not be a candidate foractivation.

[1767] A QA is run as follows:

[1768] 1. If this is a different control than the previous activecontrol, reset the prompt Count value.

[1769] 2. Increment the Prompt count value

[1770] 3. If PromptSelectFunction is specified, call the function andset the Prompt's inlinePrompt to the returned string.

[1771] 4. If a Reco object is present, start it. This Reco shouldalready include any active command grammar.

[1772] 5. Start the DMTF object if present. (Same concerns apply withregard to command Dtmf grammars).

[1773] A Validator (either a CompareValidator or a CustomValidator) isactive if:

[1774] 1. The SemanticItemToValidate has not been validated by thisvalidator.

[1775] A CompareValidator is run as follows:

[1776] 1. Compare the values of the ElementToCompare or ValueToCompareand SemanticItemToValidate ToValidate according to the validator'sOperator.

[1777] 2. If the test returns false, empty the text field of theSemanticItemToValidate (or both if the InvalidateBoth flag is set) andplay the prompt.

[1778] 3. If the test returns true, mark the SemanticItemToValidate asvalidated by this validator.

[1779] A CustomValidator is run as follows:

[1780] 1. The ClientValidationFunction is called with the value of theSemanticItemToValidate.

[1781] 2. If the function returns false, the semanticItem cleared andthe prompt is played, otherwise as validated by this validator.

[1782] A Command is considered active if and only if:

[1783] 1. It is in Scope, AND

[1784] 2. There is not another Command of the same Type lower in thescope tree.

[1785] 22.2 LastComnmandOrException

[1786] LastCommandOrException is a global variable and its value ispassed to several author-defined functions as a parameter.

[1787] LastCommandOrException is a global variable maintained byRunSpeech. The value is set to the last Command.Type or recognitionexception that occurred. The value will be reset to “ ” when there is aQA transition (the current active QA is different than the previouslyactive QA, or is the first active QA). There is one exception to thisrule: If the QA is in a Short time-out confirmation state, and thecurrent recognition result is “Silence”, the LastCommandOrException willbe set to “ ” (silence in Short time-out confirmation is not anexception, but a valid input.)

[1788] In this fashion, ClientActivationFunction will always get theLastCommandOrException that occurred anywhere in the page, but the restof the functions of the active QA will only get a non-emptyLastCommandOrException if they have been activated more than once in arow.

[1789] If, after processing all the Answers, ExtraAnswers and Confirmsin a QA, nothing is matched (either due to a mismatch in the smlreturned or to a high reject threshold), the LastCommandOrException willbe set to “NoReco”.

[1790] Active Validators will also reset the globalLastCommandOrException.

[1791] Possible values of LastCommandOrException are: platform eventLastCommandOrException Prompt fires an onerror event “PromptError”. Recofires an onerror event “RecoError”. Dtmf fires an onerror event“DtmfError”. Reco fires an onnoreco event “NoReco”. Reco fires a silenceevent “Silence”. Command is Activated Command.type Transition to new QA“”

[1792] Also, a PromptSelectFunction's LastCommandOrException will havethe value “ShortTimeoutConfirmation” when its QA is in Short Time-outConfirmation mode (i.e., when count=, firstInitialTimeout is non-zero,etc.)

[1793] 22.3 Count

[1794] Count is exclusively local—both in ClientActivationFunction andthe rest of the functions which are passed count. That is, thesefunctions are always passed the count of their own QA. To avoidconfusion, the function ClientActivationFunction will receive the valuethat the PromptSelectFunction would receive if this QA was active.

[1795] 22.4 Postback Support

[1796] In their simplest form, ASP.NET pages are stateless. They areinstantiated, executed, rendered, and disposed of on every round trip tothe server. In the visual world, ASP.NET provides the ViewStatemechanism to keep track of server control state values that don'totherwise postback as part of an HTTP form. The ASP.NET framework usesViewState to manage and restore page properties prior to and afterpostback.

[1797] For voice-only pages, the ASP.NET ViewState mechanism is notavailable to the web developer. However, a similar mechism is providedby RunSpeech. RunSpeech maintains an object that can be used to storevalues which authors wish to be persisted across postbacks. The syntaxis:

[1798] RunSpeech.ClientViewState[[“MyVariableName”]=myVariableValue;

[1799] Any JScript built-in type can be persisted—string, number,boolean, array, object, Date, RegExp, or function. The main differencebetween the ASP.NET ViewState (for visual pages) and the voice-onlyClientViewState mechanism is that authors of voice-only pages mustmanually declare and set values they wish to maintain across postbacks.

[1800] If AutoPostBack is set to true in any speech control, thematching client-side function will always be executed before postingback to the server. If the author wishes to persist any page stateacross postback, these client-side functions are a good place to invokethe ClientViewState object of RunSpeech.

[1801] 23 Confirmation Algorithm

[1802] Semantic Processing Algorithm:

[1803] There are three stages for semantic processing:

[1804] 1) Preprocessing, Carried Out when a QA is Active:

[1805] This stage is responsible for creating the array of answers to beconsidered in this iteration. This includes all the Answers and theConfirms that need confirmation. Internally, it creates a structure asfollows. Answer ID CurrentValue Answer ID CurrentValue

[1806] This information that is also passed to the PromptSelectFunction,GrammarSelectFunction, etc.

[1807] 2) Answer Processing

[1808] In this stage, we process the Answer objects in the Answers andExtraAnswers collections. If any item from the Answers collection ismatched, a flag indicating this fact is set. Answer processing sets theconfirmation status of the associated semantic item—this status can beeither NEEDS_CONFIRMATION or CONFIRMED. If the confidence valueassociated with the smlNode specified by the Answer's XpathTrigger isless than or equal to the Answer's confirmationThreshold, the status ofthe semantic item is set to NEEDS_CONFIRMATION. Otherwise it is set toCONFIRMED.

[1809] 3) Confirmation Processing:

[1810] a) Examine at the sml document and search for XpathAcceptConfirmsand XpathDenyConfirms. Set a global confirmation state to NEUTRAL (nonewas present), ACCEPT (xpathAcceptConfirms was present) or DENY(XPathDenyConfirms was present). In short-timeout confirmation, silencesets the confirmation state to ACCEPT.

[1811] b) For all items to be confirmed,

[1812] If there is a value in the sml document that matches theXpathTrigger of the confirm item

[1813] If the new value is the same as the value to be confirmed, theitem is confirmed

[1814] Else, the item is set to the new value, and processed as ananswer.

[1815] c) If no Answer object is matched from the Answers or Confirmscollections,

[1816] If the confirmation state is CONFIRM

[1817] Upgrade all items that need confirmation to confirmed.

[1818] If the confirmation state is DENY

[1819] Clear (empty) all items that need confirmation.

[1820] Else,

[1821] Mark all unmatched items that needed confirmation as confirmed.

[1822] 24 Exceptions

[1823] The following table lists the exceptions thrown by SpeechControls during render time. Attribute/Method/ Control/object ObjectCondition Exception QA SpeechIndex SpeechIndex <0ArgumentOutOfRangeException XpathDenyConfirms XpathDenyConfirmsArgumentNullException not specified if Confirm specified Answers Answerscollection ArgumentException contains a non- answer object Prompt Promptnon- ArgumentNullException existant in Voice- only mode QAFirstInitialTimeout FirstInitialTimeout InvalidOperationExceptionspecified without Confirms being specified FirstInitialTimeoutFirstInitialTimeout <0 ArgumentOutOfRangeException AcceptRejectThresholdAcceptRejectThreshold ArgumentOutOfRangeException <0 or >1DenyRejectThreshold DenyRejectThreshold ArgumentOutOfRangeException <0or >1 Command SpeechIndex SpeechIndex <0 ArgumentOutOfRangeExceptionScope Scope not valid ArgumentException Scope Scope notArgumentNullException specified Type Type not specifiedArgumentNullException Type/Scope More than 1 InvalidOperationExceptionCommand of same Type has same Scope AcceptCommandThresholdAcceptCommandThreshold ArgumentOutOfRangeException <0 or >1 XpathTriggerXpathTrigger not ArgumentNullException specified AutoPostBackAutoPostBack is InvalidOperationException true and Triggered handler notspecified AutoPostBack AutoPostBack is InvalidOperationException falseand Triggered handler is specified CompareValidator SpeechIndexSpeechIndex <0 ArgumentOutOfRangeException SemanticItemToCompare one ofInvalidOperationException SemanticltemToCompare and ValueToCompare isnot specified ValueToCompare one of InvalidOperationExceptionSemanticItemToCompare and ValueToCompare is not specified ValueToCompareValueToCompare can InvalidOperationException not be converted to a validType. SemanticItemToValidate SemanticItemToValidateArgumentNullException not specified CustomValidator SpeechIndexSpeechIndex <0 ArgumentOutOfRangeException SemanticItemToValidateSemanticItemToValidate ArgumentNullException not specifiedClientValidationFunction ClientValidationFunction ArgumentNullExceptionnot specified Answer XpathTrigger XpathTrigger not ArgumentNullExceptionobject specified for Answers or ExtraAnswwers ConfirmThresholdConfirmThreshold ArgumentOutOfRangeException <0 or >1 Reject Reject <0or >1 ArgumentOutOfRangeException AutoPostBack Answer.TriggeredInvalidOperationException has a handler but Answer.AutoPostBac k isfalse SemanticItem TargetElement TargetElement object specifies multipleids TargetAttribute TargetAttribute is ArgumentNullException notspecified when TargetElement is specified BindAt BindAt set to anArgumentException invalid value BindAt BindAt is “server”ArgumentException and SemanticItem.TargetElement is not a server-sidecontrol BindAt BindAt is “server” ArgumentException andSemanticItem.TargetAttribute is not a member of the control specified bySemanticItem.TargetElement BindAt BindAt is “server” ArgumentExceptionand SemanticItem.TargetAttribute is a member ofSemanticItem.TargetElement, but is not of type string, BindAt BindAt is“server” ArgumentException and SemanticItem.TargetAttribute is a string,but is read-only. Reco object initialTimeout initialTimeoutArgumentOutOfRangeException negative babbleTimeout babbleTimeoutArgumentOutOfRangeException negative maxTimeout maxTimeoutArgumentOutOfRangeException negative endSilence endSilenceArgumentOutOfRangeException negative reject reject <0 or >1ArgumentOutOfRangeException Grammars Grammars ArgumentExceptioncollection contains a non- grammar object Params name not specifiedArgumentNullException Params contains a non- ArgumentException paramobject Grammar src/InlineGrammar one of src or ArgumentNullExceptionobject InlineGrammar is not specified Prompt Params name not specifiedArgumentNullException object Params contains a non- ArgumentExceptionparam object Dtmf object initialTimeout initialTimeout <0ArgumentOutOfRangeException interdigitTimeout interdigitTimeoutArgumentOutOfRangeException <0 endSilence endSilence <0ArgumentOutOfRangeException Params name not specifiedArgumentNullException Params contains a non- ArgumentException paramobject \ StyleSheet contains an object ArgumentException which is not aStyle object Style object StyleReference StyleReference isArgumentException invalid SmexMessageBase Timer Timer <0ArgumentOutOfRangeException SmexMessage Message Message notArgumentNullException specified MakeCall CalledDirectoryNumberCalledDirectoryNumber ArgumentNullException not specified

[1824] 26 Terms and Defintions Term Definition Voice-only A mode ofdialog that utilizes only speech input and ouput. There are no visualelements presented to the end user. Voice-only dialog typically impliesthe end user communication via the telephone. However, voice-onlyinteraction may occur in a desktop computer setting. Multimodal A modeof dialog that utilizes speech input and visual ouput. Multimodaltypically implies end user communication with a dialog via a hand-heldcomputing device such as a pocket PC. Tap-and-talk A form of dialoginteraction that utilizes speech input and visual ouput. This form ofdialog interaction typically occurs on a hand-held computer such apocket PC. The end user selects (“taps”) the visual element with astylus or pen-like device and provides input to the visual element usingspeech (“talk”). Mixed A form of dialog interaction model, whereby theuser Initiative is permitted to share the dialog initiative with thesystem, eg by providing more answers than requested by a prompt, or byswitching task when not prompted to do so. SAPI SML SAPI Semantic markuplanguage. The XML document returned by SAPI 6.0 when an utterance isdetermined to be in-grammar. (SAPI SML is a SAPI-specific return format.Speech tags interpreters are agnostic to the actual content format ofthe returned document, provided it is an XML document). SAPI SMLcontains semantic values, confidence scores and the words used by thespeaker. (It is generated by script or XSLT instructions containedwithin the grammar rules.) SAPI SML is described in greater detail inthe Speech Core document SML Generation.. CSTA Computer SupportedTelecommunications Applications — an ECMA standard. From the ECMAdocument: “CSTA is an interface that provides access totelecommunication functions that may be used with your phone (or manyother communication devices) and may also be used by 3rd partyapplications such as Contact/Call Centres (e.g. ACD systems).”http://www.ecma.ch/ecma1/TOPICS/TC32/TG11/CSTA. HTM System A form ofdialog interaction model, whereby the Initiative system holds theinitiative, and drives the dialog with typically simple questions towhich only a single answer is possible. XPath XML Path language, a W3Crecommendation for addressing parts of an XML document. Seehttp://www.w3.org/TR/xpath.

[1825] 27 Platform Parameter Settings

[1826] The <param> mechanism (described in sections Error!

[1827] Reference source not found. Prompt object contents, Error!

[1828] Reference source not found. Reco object contents and Error!

[1829] Reference source not found. Dtmf object contents)31 is used toconfigure platform settings. The following “params” are recognized byall Microsoft platforms: Object Name Value Default Description Promptserver URI http://localhost This configuration describing (client)setting selects the the location and registry speech server used of thespeech setting for speech processing server (telephony server) bargeinThis The default The barge-in types type attribute setting is aredefined as: sets the type “speech”. If speech: This of the platformrepresents recognition does not speech/sound/energy input event supportthe (“SOUND_START”) that the type detected by the browser uses selected,the recognition engine. to determine browser grammar: This whether andefaults to represents the audio onbargein “speech”. partially matchingevent should the recognition be fired. grammar. The speech There areserver will generate three types a “PHRASE_START” of event, and possiblya bargeintype semantic event (a that can be semantic property in set:the phrase hypothesis “speech”, has confidence “grammar” greater thanthe and “final”. confidence threshold). The client decides when to throw“onbargein” based on the capabilities sent by the speech server when asession is opened. The confidence threshold used by the semantic eventis a client platform setting. final: This represents using a “valid”final recognition result (i.e. a result where the utterance confidencelevel is above the “reject” threshold). Run in conjunction with multiplerecognition mode, this represents the recognizer continuously listeningfor a valid result, for hotword/wake-up style scenarios. Note that inthis case the browser must fire onbargein before firing onreco. Recoserver URI http://localhost This configuration describing (client)setting selects the the location and registry speech server used of thespeech setting for speech processing server (telephony server)

[1830] 28 DET Descriptions

[1831] The following table lists brief descriptions for each control,object and attribute. These descriptions will be used by the DET tooland exposed to the dialog author using Visual Studio. Control/objectAttribute/Method/Object Brief description QA Id Programmatic name of thecontrol SpeechIndex Activation order of the controlClientActivationFunction Client-side function used to determine whetheror not to activate the QA control OnClientActive Client-side functioncalled after QA is determined to be active OnClientComplete Client-sidefunction called after execution of QA (successfully or not).OnClientListening Client-side function called after successful start ofthe reco object AllowCommands Whether or not Commands may be activatedfor this QA PlayOnce Whether or not this QA may be activated more thanonce per page XpathAcceptConfirms The path in the sml document thatindicates the confirm items were accepted XpathDenyConfirms The path inthe sml document that indicates the confirm items were deniedFirstInitialTimeout Specifies initial timeout when QA. Count==1. AnswersAn array of answer objects ExtraAnswers An array of answer objectsConfirms An array of answer objects. Prompt The Prompt object for thisQA Reco The Reco object for this QA Dtmf The Dtmf object for this QACommand Id Programmatic name of the control SpeechIndex Activation orderof the control Scope The id of ASP.NET control that activates thisCommand grammar Type The type of this Command in order to allow theoverriding of identically typed commands XpathTrigger SML document paththat triggers this command AcceptCommandThreshold Confidence level ofrecognition that is necessary to trigger this command OnClientCommandFunction to execute on recognition of this Command's grammarAutoPostBack Whether or not Command control posts back to server whenCommand grammar is recognized. Prompt A Prompt object Grammar Thegrammar object which will listen for the command Dtmf The Dtmf objectwhich will activate the command CompareValidator Id Programmatic name ofthe control SpeechIndex Activation order of the control Type Sets thedatatype of the comparison ElementToCompare The JScript variable or Idof the SemanticItem used as the basis for the comparisonSemanticItemToValidate The Id of the control that is being validatedSemanticItemToCompare The Id of the control that is the basis forcomparison Operator Validation operator InvalidateBoth Whether or not toinvalidate both ElementToCompare and ElementToValidate Prompt Prompt toindicate the error CustomValidator id Programmatic name of the controlSpeechIndex Activation order of the control SemanticItemToValidate TheId of the control that is being validated AttributeToValidate Attributeof the ElementToValidate that contains the value being validatedClientValidationFunction Validation function Prompt Prompt to indicatethe error Answer object id Programmatic name of the object XpathTriggerThe part of the SML document this answer refers toClientNormalizationFunction Function that returns author- specifiedtransformation of the recognized item SemanticItem The semantic item towhich this answer should be written ConfirmThreshold The minimumconfidence level of recognition necessary to mark this item as confirmedReject Rejection threshold for the Answer OnClientAnswer Function to becalled when the XpathTrigger is matched AutoPostBack Whether or not topost back to the server each time user interacts with the control Promptobject id Programmatic name of the object type Mime-type correspondingto the speech output format prefetch Whether or not the prompt should beimmediately synthesized and cached at browser when the page is loadedlang The language of the prompt content bargein Whether or not thespeech platform is responsible for stopping prompt playback when speechor DTMF input is detected. PromptSelectFunction Function that selectsand/or modifies a prompt string prior to playback OnClientBookmarkFunction which is called when a bookmark is reached in the prompt textduring playback OnClientError Function called in response to an errorevent in the client InLinePrompt Text of the prompt Params Specifiesnon-standard speech platform configuration values Reco object IdProgrammatic name of the object StartElement Name of the GUI element tothrow the start event StartEvent Name of the GUI event that willactivate the underlying client- side Reco object StopElement Name of theGUI element to throw the stop event StopEvent Name of the GUI event thatwill deactivate the underlying client- side Reco object initialTimeoutThe time in milliseconds between start of recognition and the detectionof speech babbleTimeout The period of time in milliseconds in which therecognizer must return a result after detection of speech maxTimeout Theperiod of time in milliseconds between recognition start and resultsreturned to the browser endSilence Period of silence in millisecondsafter the end of an utterance which the recognition results are returnedReject The rejection threshold below which the platform will throw thenoReco event Lang The language of the speech recognition engine ModeSpecifies the recognition mode to be followed GrammarSelectFunctionClient-side function called prior to starting the recognition processOnClientSilence Client-side function that will be called after detectingsilence OnClientNoReco Client-side function that will be called afterdetecting no recognition OnClientError Client-side function that will becalled after recognition errors OnClientSpeechDetected Client-sidefunction called when recognition platform detects speech Grammars Anarray of grammar objects. Params Specifies non-standard speech platformconfiguration values Record Used for recording audio input from theuser. Grammar id Programmatic name of the object type Mime-type of thegrammar format used lang Language of the grammar src URI of the grammarto load InLineGrammar Text of the grammar Dtmf object id Programmaticname of the object numDigits Number of key presses required to end theDTMF collection session autoflush Whether or not to automatically flushthe DTMF buffer on the underlying telephony interface card beforeactivation terminalChar Terminating key to end the DTMF collectionsession initialTimeout Number of milliseconds to wait between activationand the first key press before raising a timeout event interdigitTimeoutNumber of milliseconds to wait between key presses before raising atimeout event SMLContext DTMF results wrapped in SML tagsOnClientSilence Function that executes if there is no DTMF key pressbefore initialTimeout expires OnClientKeyPress Function that executes onevery pressing of a legal DTMF key. OnClientError Function that executesif serious or fatal error occurs with the DTMF collection/recognitionprocess Params Params Specifies non-standard DTMF engine configurationvalues name The name of the parameter to be configured. record Value Thevalue assigned to the named parameter enabled Whether or not to recorduser input. type MIME type of the file containing the recorded audio.Whether or not to play a beep before recording begins.

What is claimed is:
 1. A computer readable medium having instructions,which when executed on a computer generate client side markup for aclient in a client/server system, the instructions comprising: a set ofcontrols for rendering, each control having a first set of attributesrelated to visual rendering and a second set of attributes related to atleast one of recognition and audibly prompting.
 2. The computer readablemedium of claim 1 wherein one of the second set of attributes for one ofthe controls relates to a grammar to use for recognition.
 3. Thecomputer readable medium of claim 2 wherein said one of the second setof attributes provides a reference to a location of the grammar.
 4. Thecomputer readable medium of claim 2 wherein the grammar is for one ofspeech recognition, handwriting recognition, gesture recognition andvisual recognition.
 5. The computer readable medium of claim 4 whereinthe controls relate to one of HTML, XHTML, cHTML, XML and WML.
 6. Thecomputer readable medium of claim 1 wherein the controls relate to oneof HTML, XHTML, cHTML, XML and WML.
 7. The computer readable medium ofclaim 1 wherein one of the second set of attributes for one of thecontrols provides instructions related to generating audible output. 8.The computer readable medium of claim 7 wherein the instructionscomprise text and the attribute relates to converting the text toaudible output.
 9. The computer readable medium of claim 1 wherein oneof the second set of attributes for one of the controls relates to alocation of data for audible output.
 10. The computer readable medium ofclaim 9 wherein the data comprises a prerecorded audio data file and theattribute relates to playing the prerecorded audio data file.
 11. Thecomputer readable medium of claim 9 wherein the data comprises text andthe attribute relates to converting the text to audible output.
 12. Acomputer readable medium having instructions, which when executed on acomputer generate client side markup for a client in a client/serversystem, the instructions comprising: a first set of visual controlshaving attributes for visual rendering on the client device; and asecond set of controls having attributes related to at least one ofrecognition and audibly prompting, the second set of controls using atleast one of the first set of controls.
 13. The computer readable mediumof claim 12 wherein one of the attributes for the second set of controlsrelates to a grammar to use for recognition.
 14. The computer readablemedium of claim 13 wherein said one of the attributes provides areference to a location of the grammar.
 15. The computer readable mediumof claim 13 wherein the grammar is for one of speech recognition,handwriting recognition, gesture recognition and visual recognition. 16.The computer readable medium of claim 15 wherein the first set ofcontrols and the second set of controls relate to one of HTML, XHTML,cHTML, XML and WML.
 17. The computer readable medium of claim 12 whereinthe controls relate to one of HTML, XHTML, cHTML, XML and WML.
 18. Thecomputer readable medium of claim 12 wherein one of the second set ofattributes for one of the controls provides instructions related togenerating audible output.
 19. The computer readable medium of claim 18wherein the instructions comprise text and the attribute relates toconverting the text to audible output.
 20. The computer readable mediumof claim 12 wherein one of the second set of attributes for one of thecontrols relates to a location of data for audible output.
 21. Thecomputer readable medium of claim 20 wherein the data comprises aprerecorded audio data file and the attribute relates to playing theprerecorded audio data file.
 22. The computer readable medium of claim20 wherein the data comprises text and the attribute relates toconverting the text to audible output.
 23. A computer readable mediumhaving instructions, which when executed on a computer generate clientside markup for a client in a client/server system, the instructionscomprising: a first set of visual controls having attributes for visualrendering on the client device; and a second set of controls havingattributes related to at least one of recognition and audibly prompting,the second set of controls are selectively associated with the first setof controls.
 24. The computer readable medium of claim 23 wherein one ofthe attributes for the second set of controls relates to a grammar touse for recognition.
 25. The computer readable medium of claim 24wherein said one of the attributes provides a reference to a location ofthe grammar.
 26. The computer readable medium of claim 24 wherein thegrammar is for one of speech recognition, handwriting recognition,gesture recognition and visual recognition.
 27. The computer readablemedium of claim 26 wherein the first set of controls and the second setof controls relate to one of HTML, XHTML, cHTML, XML and WML.
 28. Thecomputer readable medium of claim 23 wherein the controls relate to oneof HTML, XHTML, cHTML, XML and WML.
 29. The computer readable medium ofclaim 23 wherein one of the second set of attributes for one of thecontrols provides instructions related to generating audible output. 30.The computer readable medium of claim 29 wherein the instructionscomprise text and the attribute relates to converting the text toaudible output.
 31. The computer readable medium of claim 23 wherein oneof the second set of attributes for one of the controls relates to alocation of data for audible output.
 32. The computer readable medium ofclaim 31 wherein the data comprises a prerecorded audio data file andthe attribute relates to playing the prerecorded audio data file. 33.The computer readable medium of claim 31 wherein the data comprises textand the attribute relates to converting the text to audible output. 34.The computer readable medium of claim 23 wherein one of the attributesof the second set of controls relates to an identifier of the associatedcontrol of the first set of controls to form the association.
 35. Thecomputer readable medium of claim 23 wherein one of the attributesrelates to whether the associated control of the second set is availablefor activation.
 36. The computer readable medium of claim 35 whereinactivation relates to generating markup.
 37. The computer readablemedium of claim 35 wherein activation relates to execution on theclient.
 38. The computer readable medium of claim 23 wherein the secondset of controls activates another control of the second set.
 39. Thecomputer readable medium of claim 23 wherein the second set of controlscomprise: a control for generating markup related to audible promptingof a question and for generating markup related to a grammar forrecognition. 39a. The computer readable medium of claim 23 wherein thesecond set of controls comprise: a question control for generatingmarkup related to audible prompting of a question; and an answer controlfor generating markup related to a grammar for recognition.
 40. Thecomputer readable medium of claim 39a wherein the question controlactivates the answer control.
 41. The computer readable medium of claim40 wherein the answer control includes a mechanism to associate areceived result with one of the first set of controls.
 42. The computerreadable medium of claim 41 wherein mechanism includes binding therecognition value.
 43. The computer readable medium of claim 42 whereinthe mechanism includes issuing an event related to operation of binding.44. The computer readable medium of claim 23 wherein the second set ofcontrols includes means defining a command for generating markup relatedto a grammar for one of navigation in the markup, help with a task, andrepeating an audible prompt.
 45. The computer readable medium of claim23 wherein the second set of controls includes means for defining aconfirmation for generating markup related to confirming that arecognized result is correct.
 46. The computer readable medium of claim45 wherein the confirmation is activated as a function of a confidencelevel of the recognized result.
 47. The computer readable medium ofclaim 46 wherein one of the controls of the second set of controlsincludes an attribute related to a confidence level.
 48. The computerreadable medium of claim 23 wherein the second set of controls includesmeans for defining a comparison for generating markup for comparing arecognized result with a selected value.
 49. The computer readablemedium of claim 23 wherein the second set of controls includes means fordefining a comparison for generating markup for comparing a recognizedresult with another recognized result.
 50. The computer readable mediumof claim 23 wherein the second set of controls includes means formaintaining a recognized result apart from the associated control of thefirst set of controls, said means for maintaining associating therecognized result with the control of the first set of controls.
 51. Thecomputer readable medium of claim 50 wherein the means for maintainingthe recognized result includes means for indicating that the recognizedresult has changed. 51a. The computer readable medium of claim 50wherein the means for maintaining the recognized result includes meansfor indicating that the recognized result has been confirmed. 51b. Thecomputer readable medium of claim 50 and means for maintaining arecognized result includes maintaining a set of items for correspondingrecognized results, and wherein at least some of the items areindividually associated with controls of the first set of controls, andwherein states are maintained for at least some of the items, the statesincluding if the item is empty and if the item has been confirmed.
 52. Acomputer implemented method for defining a website application on aserver in a server/client architecture, the website applicationproviding markup to a client for performing recognition and/or audibleprompting on the client, the method comprising: defining the websiteapplication with a first set of visual controls having attributes forvisual rendering on the client device with a second set of controlsrelated to at least one of recognition and audibly prompting; andselectively associating controls of the second set of controls with atleast one control of the first set of visual controls.
 53. The computerimplemented method of claim 52 wherein each of the controls of thesecond set include an identifier attribute for identifying a control ofthe first set of visual controls, and wherein associating includesproviding an identifier of at least one control of the first set ofcontrols in the corresponding identifier attribute of each of the secondset of controls.
 54. The computer implemented method of claim 52 whereinthe second set of controls includes a control related to audibleprompting of a question and a grammar for recognition; and whereindefining the website application with a second set of controls relatedto at least one of recognition and audibly prompting includesassociating said control related to audible prompting of the questionand the grammar for recognition with one of the controls of the firstset of controls.
 55. The computer implemented method of claim 54 whereinthe second set of controls includes means for confirming that arecognized result is correct; and wherein defining the websiteapplication with a second set of controls related to at least one ofrecognition and audibly prompting includes associating the means forconfirming with a recognized result to be received. 55a. The computerimplemented method of claim 55 wherein defining the website applicationwith a second set of controls related to at least one of recognition andaudibly prompting includes defining a confidence level for activation ofsaid means for confirming.
 56. The computer implemented method of claim54 wherein the second set of controls includes means for generatingmarkup related to a grammar for one of navigation on the computer, helpwith a task, and repeating an audible prompt; and wherein defining thewebsite application with a second set of controls related to at leastone of recognition and audibly prompting includes associating said meanswith means for prompting a question control.
 57. The computerimplemented method of claim 54 wherein the second set of controlsincludes means for comparing a recognized result with a selected value;and wherein defining the website application with a second set ofcontrols related to at least one of recognition and audibly promptingincludes associating the means for confirming with a recognized resultto be received.
 58. The computer implemented method of claim 54 whereinthe second set of controls includes means for comparing a recognizedresult with another recognized result; and wherein defining the websiteapplication with a second set of controls related to at least one ofrecognition and audibly prompting includes associating the means forconfirming with a recognized result to be received.
 59. The computerimplemented method of claim 54 wherein the second set of controlsincludes wherein the second set of controls includes means formaintaining a set of items for corresponding recognized results apartfrom the associated controls of the first set of controls; and whereindefining the website application with a second set of controls relatedto at least one of recognition and audibly prompting includesassociating at least some of the items with controls of the first set ofcontrols.